Change WorkTableScan to not support backward scan. The apparent support
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Oct 2008 17:13:51 +0000 (17:13 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 28 Oct 2008 17:13:51 +0000 (17:13 +0000)
commitad3ce0efddb96857bf3d76acb496a1df260c2de9
treeaa444b365e2df520092685440b37f27f78dfb9ea
parent5230c754b8e4022e5c0608fc212bdab2cd06f652
Change WorkTableScan to not support backward scan.  The apparent support
didn't actually work, because nodeRecursiveunion.c creates the underlying
tuplestore with backward scan disabled; which is a decision that we shouldn't
reverse because of performance cost.  We could imagine adding signaling from
WorkTableScan to RecursiveUnion about whether backward scan is needed ...
but in practice it'd be a waste of effort, because there simply isn't any
current or plausible future scenario where WorkTableScan would be called on
to scan backward.  So just dike out the code that claims to support it.
src/backend/executor/execAmi.c
src/backend/executor/nodeWorktablescan.c