From 493f72606b463a75ae4e2ee4e64d829e7f56066d Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Sat, 11 Sep 2004 18:28:34 +0000
Subject: Renumber SnapshotNow and the other special snapshot codes so that
 ((Snapshot) NULL) can no longer be confused with a valid snapshot, as per my
 recent suggestion.  Define a macro InvalidSnapshot for 0. Use InvalidSnapshot
 instead of SnapshotAny as the do-nothing special case for heap_update and
 heap_delete crosschecks; this seems a little cleaner even though the behavior
 is really the same.

---
 src/backend/executor/execMain.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'src/backend/executor/execMain.c')

diff --git a/src/backend/executor/execMain.c b/src/backend/executor/execMain.c
index d77bc7054a3..b009e73e105 100644
--- a/src/backend/executor/execMain.c
+++ b/src/backend/executor/execMain.c
@@ -26,7 +26,7 @@
  *
  *
  * IDENTIFICATION
- *	  $PostgreSQL: pgsql/src/backend/executor/execMain.c,v 1.236 2004/08/29 05:06:42 momjian Exp $
+ *	  $PostgreSQL: pgsql/src/backend/executor/execMain.c,v 1.237 2004/09/11 18:28:34 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -176,7 +176,7 @@ ExecutorStart(QueryDesc *queryDesc, bool useCurrentSnapshot, bool explainOnly)
 	{
 		/* normal query --- use query snapshot, no crosscheck */
 		estate->es_snapshot = CopyQuerySnapshot();
-		estate->es_crosscheck_snapshot = SnapshotAny;
+		estate->es_crosscheck_snapshot = InvalidSnapshot;
 	}
 
 	/*
-- 
cgit v1.2.3