On Wed, Dec 16, 2015 at 12:26 AM, Robert Haas <robertmh...@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. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
replslot_iolwlock_tranche_v1.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
