Re: [HACKERS] Should we cacheline align PGXACT?
От | Alexander Korotkov |
---|---|
Тема | Re: [HACKERS] Should we cacheline align PGXACT? |
Дата | |
Msg-id | CAPpHfdt-8Mdt0ypwTmgdpQc1REiTc5AsFgJjags8ym0J7BPaYw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Should we cacheline align PGXACT? (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Should we cacheline align PGXACT?
|
Список | pgsql-hackers |
On Tue, Feb 14, 2017 at 3:57 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Yes, but I can't use such macro in the definition of PGXACT itself.
Alexander Korotkov wrote:
> On Mon, Feb 13, 2017 at 7:07 PM, Alvaro Herrera <alvherre@2ndquadrant.com>
> wrote:
> > Re the coding of the padding computation, seems it'd be better to use
> > our standard "offsetof(last-struct-member) + sizeof(last-struct-member)"
> > rather than adding each of the members' sizes individually.
>
> It was done so in order to evade extra level of nesting for PGXACT. See
> discussion with Tom Lane in [1] and upthread.
Yes, I understand. I just mean that it could be done something like
this:
#define PGXACTPadSize (PG_CACHE_LINE_SIZE - (offsetof(PGXACT, nxid) + sizeof(uint8)))
The Russian Postgres Company
В списке pgsql-hackers по дате отправления: