Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?
Дата
Msg-id CAPpHfdu1Ycoa8BxxLHPnh7bhgM4BLkXEwU9Xo+C1A9KB0C4B_Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?  (Ildar Musin <i.musin@postgrespro.ru>)
Ответы Re: [HACKERS] Challenges preventing us moving to 64 bit transactionid (XID)?  (Alexander Korotkov <a.korotkov@postgrespro.ru>)
Список pgsql-hackers
Hi, Ildar!

On Tue, Sep 5, 2017 at 12:55 PM, Ildar Musin <i.musin@postgrespro.ru> wrote:
On 22.06.2017 18:36, Alexander Korotkov wrote:
On Wed, Jun 7, 2017 at 11:33 AM, Alexander Korotkov
<a.korotkov@postgrespro.ru <mailto:a.korotkov@postgrespro.ru>> wrote:

0002-heap-page-special-1.patch
Putting xid and multixact bases into PageHeaderData would take extra 16
bytes on index pages too.  That would be waste of space for indexes.
This is why I decided to put bases into special area of heap pages.
This patch adds special area for heap pages contaning prune xid and
magic number.  Magic number is different for regular heap page and
sequence page.

We've discussed it earlier but it worth mentioning here too. You have pd_prune_xid of type TransactionId which is treated elsewhere as ShortTransactionId (see HeapPageGetPruneXid() and HeapPageSetPruneXid()) and hence introduces redundant 4 bytes. Could you please fix it?

Thank you for pointing.
Updated patchset is attached.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
 
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jesper Pedersen
Дата:
Сообщение: Re: [HACKERS] Fix performance degradation of contended LWLock on NUMA
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list