This reverts commit
d573e239f03506920938bf0be56c868d9c3416da, "Take fewer
snapshots". While that seemed like a good idea at the time, it caused
execution to use a snapshot that had been acquired before locking any of
the tables mentioned in the query. This created user-visible anomalies
that were not present in any prior release of Postgres, as reported by
Tomas Vondra. While this whole area could do with a redesign (since there
are related cases that have anomalies anyway), it doesn't seem likely that
any future patch would be reasonably back-patchable; and we don't want 9.2
to exhibit a behavior that's subtly unlike either past or future releases.
Hence, revert to prior code while we rethink the problem.
</para>
</listitem>
- <listitem>
- <para>
- Take fewer <acronym>MVCC</acronym> snapshots
- (Robert Haas)
- </para>
- </listitem>
-
<listitem>
<para>
Make the number of CLOG buffers scale based on <link
/*
* Start execution, inserting parameters if any.
*/
- PortalStart(portal, params, 0, true);
+ PortalStart(portal, params, 0, GetActiveSnapshot());
Assert(portal->strategy == PORTAL_ONE_SELECT);
/*
* Run the portal as appropriate.
*/
- PortalStart(portal, paramLI, eflags, true);
+ PortalStart(portal, paramLI, eflags, GetActiveSnapshot());
(void) PortalRun(portal, count, false, dest, dest, completionTag);
CachedPlan *cplan;
List *stmt_list;
char *query_string;
+ Snapshot snapshot;
MemoryContext oldcontext;
Portal portal;
}
}
+ /* Set up the snapshot to use. */
+ if (read_only)
+ snapshot = GetActiveSnapshot();
+ else
+ {
+ CommandCounterIncrement();
+ snapshot = GetTransactionSnapshot();
+ }
+
/*
* If the plan has parameters, copy them into the portal. Note that this
* must be done after revalidating the plan, because in dynamic parameter
/*
* Start portal execution.
*/
- if (read_only)
- PortalStart(portal, paramLI, 0, true);
- else
- {
- CommandCounterIncrement();
- PortalStart(portal, paramLI, 0, false);
- }
+ PortalStart(portal, paramLI, 0, snapshot);
Assert(portal->strategy != PORTAL_MULTI_QUERY);
plantree_list = pg_plan_queries(querytree_list, 0, NULL);
+ /* Done with the snapshot used for parsing/planning */
+ if (snapshot_set)
+ PopActiveSnapshot();
+
/* If we got a cancel signal in analysis or planning, quit */
CHECK_FOR_INTERRUPTS();
NULL);
/*
- * Start the portal.
- *
- * If we took a snapshot for parsing/planning, the portal may be able
- * to reuse it for the execution phase. Currently, this will only
- * happen in PORTAL_ONE_SELECT mode. But even if PortalStart doesn't
- * end up being able to do this, keeping the parse/plan snapshot
- * around until after we start the portal doesn't cost much.
+ * Start the portal. No parameters here.
*/
- PortalStart(portal, NULL, 0, snapshot_set);
-
- /* Done with the snapshot used for parsing/planning */
- if (snapshot_set)
- PopActiveSnapshot();
+ PortalStart(portal, NULL, 0, InvalidSnapshot);
/*
* Select the appropriate output format: text unless we are doing a
cplan->stmt_list,
cplan);
- /*
- * And we're ready to start portal execution.
- *
- * If we took a snapshot for parsing/planning, we'll try to reuse it for
- * query execution (currently, reuse will only occur if PORTAL_ONE_SELECT
- * mode is chosen).
- */
- PortalStart(portal, params, 0, snapshot_set);
-
/* Done with the snapshot used for parameter I/O and parsing/planning */
if (snapshot_set)
PopActiveSnapshot();
+ /*
+ * And we're ready to start portal execution.
+ */
+ PortalStart(portal, params, 0, InvalidSnapshot);
+
/*
* Apply the result format requests to the portal.
*/
* currently only honored for PORTAL_ONE_SELECT portals). Most callers
* should simply pass zero.
*
- * The use_active_snapshot parameter is currently used only for
- * PORTAL_ONE_SELECT portals. If it is true, the active snapshot will
- * be used when starting up the executor; if false, a new snapshot will
- * be taken. This is used both for cursors and to avoid taking an entirely
- * new snapshot when it isn't necessary.
+ * The caller can optionally pass a snapshot to be used; pass InvalidSnapshot
+ * for the normal behavior of setting a new snapshot. This parameter is
+ * presently ignored for non-PORTAL_ONE_SELECT portals (it's only intended
+ * to be used for cursors).
*
* On return, portal is ready to accept PortalRun() calls, and the result
* tupdesc (if any) is known.
*/
void
PortalStart(Portal portal, ParamListInfo params,
- int eflags, bool use_active_snapshot)
+ int eflags, Snapshot snapshot)
{
Portal saveActivePortal;
ResourceOwner saveResourceOwner;
case PORTAL_ONE_SELECT:
/* Must set snapshot before starting executor. */
- if (use_active_snapshot)
- PushActiveSnapshot(GetActiveSnapshot());
+ if (snapshot)
+ PushActiveSnapshot(snapshot);
else
PushActiveSnapshot(GetTransactionSnapshot());
extern List *FetchStatementTargetList(Node *stmt);
extern void PortalStart(Portal portal, ParamListInfo params,
- int eflags, bool use_active_snapshot);
+ int eflags, Snapshot snapshot);
extern void PortalSetResultFormat(Portal portal, int nFormats,
int16 *formats);