Thread: [HACKERS] Double shared memory allocation for SLRU LWLocks

[HACKERS] Double shared memory allocation for SLRU LWLocks

From
Alexander Korotkov
Date:
Hi, all!

It seems to me that we're allocating shared memory for SLRU lwlocks twice, unless I'm missing something.

SimpleLruShmemSize() calculates total SLRU shared memory size including lwlocks size.

SimpleLruInit() starts with line

shared = (SlruShared) ShmemInitStruct(name,
                                      SimpleLruShmemSize(nslots, nlsns),
                                      &found);

which allocates SLRU shared memory (LWLocks size is included because SimpleLruShmemSize() is used for size computation).

Following line allocates shared memory for LWLocks again:
shared->buffer_locks = (LWLockPadded *) ShmemAlloc(sizeof(LWLockPadded) * nslots);

Attached patch fixes that by removing extra ShmemAlloc for SLRU.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment

Re: [HACKERS] Double shared memory allocation for SLRU LWLocks

From
Teodor Sigaev
Date:
> It seems to me that we're allocating shared memory for SLRU lwlocks twice,
> unless I'm missing something.
I think you are right.

Did you check previous versions? i.e. should it be applyed to previous 
branches?? I suppose yes, to minimize code difference.

Also I'd like an idea to add Assert(offset <= SimpleLruShmemSize(nslots, nlsns)) 
at the end of SimpleLruInit()

>
> SimpleLruShmemSize() calculates total SLRU shared memory size including lwlocks
> size.
>
> SimpleLruInit() starts with line
>
> shared = (SlruShared) ShmemInitStruct(name,
>                                       SimpleLruShmemSize(nslots, nlsns),
>                                       &found);
>
> which allocates SLRU shared memory (LWLocks size is included because
> SimpleLruShmemSize() is used for size computation).
>
> Following line allocates shared memory for LWLocks again:
> shared->buffer_locks = (LWLockPadded *) ShmemAlloc(sizeof(LWLockPadded) * nslots);
>
> Attached patch fixes that by removing extra ShmemAlloc for SLRU.
>
> ------
> Alexander Korotkov
> Postgres Professional: http://www.postgrespro.com
> The Russian Postgres Company
>
>
>

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/
 



Re: [HACKERS] Double shared memory allocation for SLRU LWLocks

From
Alexander Korotkov
Date:
On Wed, Jul 12, 2017 at 2:03 PM, Teodor Sigaev <teodor@sigaev.ru> wrote:
It seems to me that we're allocating shared memory for SLRU lwlocks twice,
unless I'm missing something.
I think you are right.

Did you check previous versions? i.e. should it be applyed to previous branches?? I suppose yes, to minimize code difference.

Problem was introduced by fe702a7b.  I think it would be good to backpatch to 9.6.  Besides it doesn't cause any user-visible problem, nevertheless it's a bug.
 
Also I'd like an idea to add Assert(offset <= SimpleLruShmemSize(nslots, nlsns)) at the end of SimpleLruInit()

Good point.  Please, find it in attached patch.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
 
Attachment