Fix latent bug in ExecSeqRestrPos: it leaves the plan node's result slot
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 15 May 2005 21:19:55 +0000 (21:19 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 15 May 2005 21:19:55 +0000 (21:19 +0000)
commit51048ab79896da2f3c6a2e47f6fa1fdd734539b8
tree7e6f06834b9f75956069dc160f4f624e3dfe7b5b
parent78fe943a933de929f4f68393679f2311577af8c1
Fix latent bug in ExecSeqRestrPos: it leaves the plan node's result slot
in an inconsistent state.  (This is only latent because in reality
ExecSeqRestrPos is dead code at the moment ... but someday maybe it won't
be.)  Add some comments about what the API for plan node mark/restore
actually is, because it's not immediately obvious.
src/backend/access/index/indexam.c
src/backend/executor/execAmi.c
src/backend/executor/nodeMergejoin.c
src/backend/executor/nodeSeqscan.c