Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

nodeWorktablescan.c

Blame
    • Tom Lane's avatar
      a80a1224
      Change WorkTableScan to not support backward scan. The apparent support · a80a1224
      Tom Lane authored
      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.
      a80a1224
      History
      Change WorkTableScan to not support backward scan. The apparent support
      Tom Lane authored
      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.