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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Robert Haas authored
    This fixes a long-standing bug which was discovered while investigating
    the interaction between the new join pushdown code and the EvalPlanQual
    machinery: if a ForeignScan appears on the inner side of a paramaterized
    nestloop, an EPQ recheck would re-return the original tuple even if
    it no longer satisfied the pushed-down quals due to changed parameter
    values.
    
    This fix adds a new member to ForeignScan and ForeignScanState and a
    new argument to make_foreignscan, and requires changes to FDWs which
    push down quals to populate that new argument with a list of quals they
    have chosen to push down.  Therefore, I'm only back-patching to 9.5,
    even though the bug is not new in 9.5.
    
    Etsuro Fujita, reviewed by me and by Kyotaro Horiguchi.
    5fc4c26d
    History
    Name Last commit Last update