Re: Writeable CTEs and empty relations - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Writeable CTEs and empty relations
Date
Msg-id 1296.1265839071@sss.pgh.pa.us
Whole thread Raw
In response to Re: Writeable CTEs and empty relations  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Writeable CTEs and empty relations
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> If the executor has buried in it the assumption that the snapshot
> can't change after startup, then does that mean that we need to start
> up and shut down the executor for each subquery?

Yes, I think so.  That's the way it's always worked in the past;
see for example PortalRunMulti() and ProcessQuery().  I think trying
to change that is a high-risk, low-reward activity.

This probably means that the planner output for queries involving
writeable CTEs has to be a separate PlannedStmt per such CTE.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Output configuration status after ./configure run.
Next
From: Marko Tiikkaja
Date:
Subject: Re: Writeable CTEs and empty relations