]> granicus.if.org Git - postgresql/commit
Use the correct tuplestore read pointer in a NamedTuplestoreScan.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 27 Feb 2018 20:56:51 +0000 (15:56 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 27 Feb 2018 20:56:51 +0000 (15:56 -0500)
commite98a4de7d23a54a6c861795ad8e920a59613e08b
tree1186827ec34fec9cd236338cca7536a8bce76dcc
parentc40e20a83ce521b5b5403b08dde05b0f0641d77f
Use the correct tuplestore read pointer in a NamedTuplestoreScan.

Tom Kazimiers reported that transition tables don't work correctly when
they are scanned by more than one executor node.  That's because commit
18ce3a4ab allocated separate read pointers for each executor node, as it
must, but failed to make them active at the appropriate times.  Repair.

Thomas Munro

Discussion: https://postgr.es/m/20180224034748.bixarv6632vbxgeb%40dewberry.localdomain
src/backend/executor/nodeNamedtuplestorescan.c
src/test/regress/expected/plpgsql.out
src/test/regress/sql/plpgsql.sql