Fix rescan logic in nodeCtescan.
The previous coding essentially assumed that nodes would be rescanned in
the same order they were initialized in; or at least that the "leader" of
a group of CTEscans would be rescanned before any others were required to
execute. Unfortunately, that isn't even a little bit true. It's possible
to devise queries in which the leader isn't rescanned until other CTEscans
on the same CTE have run to completion, or even in which the leader never
gets a rescan call at all.
The fix makes the leader specially responsible only for initial creation
and final destruction of the tuplestore; rescan resets are now a
symmetrically shared responsibility. This means that we might reset the
tuplestore multiple times when restarting a plan subtree containing
multiple CTEscans; but resetting an already-empty tuplestore is cheap
enough that that doesn't seem like a problem.
Per report from Adam Mackler; the new regression test cases are based on
his example query.
Back-patch to 8.4 where CTE scans were introduced.
src/backend/executor/nodeCtescan.c | 37 +++++++++--------
src/test/regress/expected/with.out | 75 ++++++++++++++++++++++++++++++++++++
src/test/regress/sql/with.sql | 56 +++++++++++++++++++++++++++
3 files changed, 151 insertions(+), 17 deletions(-)
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2012-08-15 23:05:07|
|Subject: pgsql: In psql, if the is no connection object,e.g. due to a server cr|
|Previous:||From: Bruce Momjian||Date: 2012-08-15 22:30:40|
|Subject: Re: [COMMITTERS] pgsql: Clean up the #include mess a