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

backend

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    right circumstances a hash join executed as a DECLARE CURSOR/FETCH
    query would crash the backend.  Problem as seen in current sources was
    that the hash tables were stored in a context that was a child of
    TransactionCommandContext, which got zapped at completion of the FETCH
    command --- but cursor cleanup executed at COMMIT expected the tables
    to still be valid.  I haven't chased down the details as seen in 7.0.*
    but I'm sure it's the same general problem.
    0147b193
    History