pgsql: Don't use SnapshotNow in get_actual_variable_range. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Don't use SnapshotNow in get_actual_variable_range.
Date
Msg-id E1V2QKO-0006Ex-DS@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Add GET DIAGNOSTICS ... PG_CONTEXT in PL/PgSQL
Next
From: Robert Haas
Date:
Subject: pgsql: pgstattuple: Use SnapshotDirty, not SnapshotNow.