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 Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/b9dac4a6eb41479d991249affe537e9861698271 Modified Files -------------- src/backend/executor/nodeNamedtuplestorescan.c | 2 ++ src/test/regress/expected/plpgsql.out | 22 ++++++++++++++++++++++ src/test/regress/sql/plpgsql.sql | 26 ++++++++++++++++++++++++++ 3 files changed, 50 insertions(+)
