]> granicus.if.org Git - postgresql/commit
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)
commita80a12247a99f0bccf47bed5786f28a35fc80845
tree5f95e0c9963fd959223a396379a8365f4eccb050
parentd26bf23f344887aecac93e9cd22b1dae64f18c83
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