Use the correct tuplestore read pointer in a NamedTuplestoreScan.
Tom Lane <tgl@sss.pgh.pa.us>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/executor/nodeNamedtuplestorescan.c | modified | +2 −0 |
| src/test/regress/expected/plpgsql.out | modified | +22 −0 |
| src/test/regress/sql/plpgsql.sql | modified | +26 −0 |
Discussion
- Unexpected behavior with transition tables in update statement trigger 9 messages · 2018-02-24 → 2018-02-27