pgsql: Relax locking during GetCurrentVirtualXIDs().

From: sriggs(at)postgresql(dot)org (Simon Riggs)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Relax locking during GetCurrentVirtualXIDs().
Date: 2010-04-21 19:08:14
Message-ID: 20100421190814.C3EBD7541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2010-04-21 19:53:25 pgsql: Only send cleanup_info messages if VACUUM removes any tuples.
Previous Message Simon Riggs 2010-04-21 17:20:56 pgsql: Fix oversight in collecting values for cleanup_info records.