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

planmain.h

  • Tom Lane's avatar
    6bdfde9a
    When testing whether a sub-plan can do projection, use a general-purpose · 6bdfde9a
    Tom Lane authored
    check instead of hardwiring assumptions that only certain plan node types
    can appear at the places where we are testing.  This was always a pretty
    fragile assumption, and it turns out to be broken in 7.4 for certain cases
    involving IN-subselect tests that need type coercion.
    Also, modify code that builds finished Plan tree so that node types that
    don't do projection always copy their input node's targetlist, rather than
    having the tlist passed in from the caller.  The old method makes it too
    easy to write broken code that thinks it can modify the tlist when it
    cannot.
    6bdfde9a
    History
    When testing whether a sub-plan can do projection, use a general-purpose
    Tom Lane authored
    check instead of hardwiring assumptions that only certain plan node types
    can appear at the places where we are testing.  This was always a pretty
    fragile assumption, and it turns out to be broken in 7.4 for certain cases
    involving IN-subselect tests that need type coercion.
    Also, modify code that builds finished Plan tree so that node types that
    don't do projection always copy their input node's targetlist, rather than
    having the tlist passed in from the caller.  The old method makes it too
    easy to write broken code that thinks it can modify the tlist when it
    cannot.