pgsql: Don't use SnapshotNow in get_actual_variable_range.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't use SnapshotNow in get_actual_variable_range.
Date: 2013-07-25 18:31:52
Message-ID: E1V2QKO-0006Ex-DS@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't use SnapshotNow in get_actual_variable_range.

Instead, use the active snapshot. Per Tom Lane, this function is
most interested in knowing the range of tuples our scan will actually
see.

This is another step towards full removal of SnapshotNow.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/3483f4332de73e038db64be0614219b64fd3c971

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2013-07-25 20:23:29 pgsql: pgstattuple: Use SnapshotDirty, not SnapshotNow.
Previous Message Tom Lane 2013-07-25 18:22:49 Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL