pgsql: Change currtid functions to use an MVCC snapshot, not SnapshotNo

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Change currtid functions to use an MVCC snapshot, not SnapshotNo
Date: 2013-07-25 20:38:11
Message-ID: E1V2SId-0008BZ-C0@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Change currtid functions to use an MVCC snapshot, not SnapshotNow.

This has a slight performance cost, but the only known consumers
of these functions, known at the SQL level as currtid and currtid2,
is pgsql-odbc; whose usage, we hope, is not sufficiently intensive
to make this a problem.

Per discussion.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/ed93feb80891b131e9676e962256cc2b18aa5e78

Modified Files
--------------
src/backend/utils/adt/tid.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-07-25 20:46:35 pgsql: Prevent leakage of SPI tuple tables during subtransaction abort.
Previous Message Robert Haas 2013-07-25 20:23:29 pgsql: pgstattuple: Use SnapshotDirty, not SnapshotNow.