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

src

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    It's not really supported to call systable_getnext() in a different
    memory context than systable_beginscan() was called in, and it's
    *definitely* not safe to do so and then reset that context between
    calls.  I'm not very clear on how this code survived
    CLOBBER_CACHE_ALWAYS testing ... but Alexander Lakhin found a case
    that would crash it pretty reliably.
    
    Per bug #15828.  Fix, and backpatch to v11 where this code came in.
    
    Discussion: https://postgr.es/m/15828-f6ddd7df4852f473@postgresql.org
    601084eb
    History