pgsql: Relax locking during GetCurrentVirtualXIDs(). - Mailing list pgsql-committers

From sriggs@postgresql.org (Simon Riggs)
Subject pgsql: Relax locking during GetCurrentVirtualXIDs().
Date
Msg-id 20100421190814.C3EBD7541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Relax locking during GetCurrentVirtualXIDs(). Earlier improvements
to handling of btree delete records mean that all snapshot
conflicts on standby now have a valid, useful latestRemovedXid.
Our earlier approach using LW_EXCLUSIVE was useful when we didnt
always have a valid value, though is no longer useful or necessary.
Asserts added to code path to prove and ensure this is the case.
This will reduce contention and improve performance of larger Hot
Standby servers.

Modified Files:
--------------
    pgsql/src/backend/storage/ipc:
        procarray.c (r1.64 -> r1.65)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/procarray.c?r1=1.64&r2=1.65)
        standby.c (r1.16 -> r1.17)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/ipc/standby.c?r1=1.16&r2=1.17)

pgsql-committers by date:

Previous
From: sriggs@postgresql.org (Simon Riggs)
Date:
Subject: pgsql: Fix oversight in collecting values for cleanup_info records.
Next
From: sriggs@postgresql.org (Simon Riggs)
Date:
Subject: pgsql: Only send cleanup_info messages if VACUUM removes any tuples.