Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Refactoring of LWLock tranches - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: [PATCH] Refactoring of LWLock tranches
Date
Msg-id CAPpHfduzPs4AnDx87Zb32-bOW7tLmDy3-b0Qb2E8fdRUvNFkAw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Refactoring of LWLock tranches  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view
On Tue, Dec 29, 2015 at 11:56 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
On Wed, Dec 16, 2015 at 12:26 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
>
> In terms of this project overall, NumLWLocks() now knows about only
> four categories of stuff: fixed lwlocks, backend locks (proc.c),
> replication slot locks, and locks needed by extensions.  I think it'd
> probably be fine to move the backend locks into PGPROC directly, and
> the replication slot locks into ReplicationSlot.
>

IIdus has written a patch to move backend locks into PGPROC which
I am reviewing and will do performance tests once he responds to
my review comments and I have written a patch to move replication
slot locks into ReplicationSlot which is attached with this mail.

This patch looks good for me.
It compiles without warnings, passes regression tests.
I also did small testing of replication slots in order to check that it works correctly.

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

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: extend pgbench expressions with functions
Next
From: Fabien COELHO
Date:
Subject: Re: pgbench stats per script & other stuff