aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execUtils.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2013-07-23 10:58:32 -0400
committerRobert Haas <rhaas@postgresql.org>2013-07-23 10:58:32 -0400
commit765ad89be36f699e2d65238c1f0458a1ab7e4d8b (patch)
tree51a0157a5efb3767283f2bfb183c1ac6d3535652 /src/backend/executor/execUtils.c
parente6055061c524698918ab0b7a0c51b822c03ef1fa (diff)
downloadpostgresql-765ad89be36f699e2d65238c1f0458a1ab7e4d8b.tar.gz
postgresql-765ad89be36f699e2d65238c1f0458a1ab7e4d8b.zip
Use InvalidSnapshot, now SnapshotNow, as the default snapshot.
As far as I can determine, there's no code in the core distribution that fails to explicitly set the snapshot of a scan or executor state. If there is any such code, this will probably cause it to seg fault; friendlier suggestions were discussed on pgsql-hackers, but there was no consensus that anything more than this was needed. This is another step towards the hoped-for complete removal of SnapshotNow.
Diffstat (limited to 'src/backend/executor/execUtils.c')
-rw-r--r--src/backend/executor/execUtils.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/executor/execUtils.c b/src/backend/executor/execUtils.c
index b449e0a5534..39e3b2e79c8 100644
--- a/src/backend/executor/execUtils.c
+++ b/src/backend/executor/execUtils.c
@@ -105,7 +105,7 @@ CreateExecutorState(void)
* Initialize all fields of the Executor State structure
*/
estate->es_direction = ForwardScanDirection;
- estate->es_snapshot = SnapshotNow;
+ estate->es_snapshot = InvalidSnapshot; /* caller must initialize this */
estate->es_crosscheck_snapshot = InvalidSnapshot; /* no crosscheck */
estate->es_range_table = NIL;
estate->es_plannedstmt = NULL;