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
    Tom Lane authored
    Commit d22a09dc introduced official support
    for GiST consistentFns that want to cache data using the FmgrInfo fn_extra
    pointer: the idea was to preserve the cached values across gistrescan(),
    whereas formerly they'd been leaked.  However, there was an oversight in
    that, namely that multiple scan keys might reference the same column's
    consistentFn; the code would result in propagating the same cache value
    into multiple scan keys, resulting in crashes or wrong answers.  Use a
    separate array instead to ensure that each scan key keeps its own state.
    
    Per bug #8143 from Joel Roller.  Back-patch to 9.2 where the bug was
    introduced.
    91715e82
    History
    Name Last commit Last update