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
    TopMemoryContext, rather than scattered through executor per-query contexts.
    This poses no danger of memory leak since the ResourceOwner mechanism
    guarantees release of no-longer-needed items.  It is needed because the
    per-query context might already be released by the time we try to clean up
    the hash scan list.  Report by ykhuang, diagnosis by Heikki.
    
    Back-patch to 8.0, where the ResourceOwner-based cleanup was introduced.
    The given test case does not fail before 8.2, probably because we rearranged
    transaction abort processing somehow; but this coding is undoubtedly risky
    so I'll patch 8.0 and 8.1 anyway.
    6a178266
    History
    Name Last commit Last update