git.ipfire.org Git - thirdparty/postgresql.git/commit

]> git.ipfire.org Git - thirdparty/postgresql.git/commit

projects / thirdparty / postgresql.git / commit

author	Tom Lane <tgl@sss.pgh.pa.us>
	Tue, 26 Dec 2006 19:27:20 +0000 (19:27 +0000)
committer	Tom Lane <tgl@sss.pgh.pa.us>
	Tue, 26 Dec 2006 19:27:20 +0000 (19:27 +0000)
commit	0fbfdf55f82cec91bd3cd1ba136e29f85f359a1a
tree	0348841bb1789affefb2e029b27f3ec89de85a28	tree \| snapshot
parent	8eb0f23a961e4c6e08191d8bf6c2a805d0c71eff	commit \| diff

Repair bug #2839: the various ExecReScan functions need to reset
ps_TupFromTlist in plan nodes that make use of it. This was being done
correctly in join nodes and Result nodes but not in any relation-scan nodes.
Bug would lead to bogus results if a set-returning function appeared in the
targetlist of a subquery that could be rescanned after partial execution,
for example a subquery within EXISTS(). Bug has been around forever :-(
... surprising it wasn't reported before.

Mirror of https://git.postgresql.org/git/postgresql.git

RSS Atom

src/backend/executor/nodeFunctionscan.c		diff \| blob \| blame \| history
src/backend/executor/nodeIndexscan.c		diff \| blob \| blame \| history
src/backend/executor/nodeResult.c		diff \| blob \| blame \| history
src/backend/executor/nodeSeqscan.c		diff \| blob \| blame \| history
src/backend/executor/nodeSubqueryscan.c		diff \| blob \| blame \| history
src/backend/executor/nodeTidscan.c		diff \| blob \| blame \| history