]> 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)
commitb9dac4a6eb41479d991249affe537e9861698271
treed6123734a2e40289cb40f83bad0b1fb474af6b30
parentd6ff2e30395bf9e68e083b2a4ba178732115531b
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