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
    Neil Conway authored
    - make sure we always invoke user-supplied GiST methods in a short-lived
      memory context. This means the backend isn't exposed to any memory leaks
      that be in those methods (in fact, it is probably a net loss for most
      GiST methods to bother manually freeing memory now). This also means
      we can do away with a lot of ugly manual memory management in the
      GiST code itself.
    
    - keep the current page of a GiST index scan pinned, rather than doing a
      ReadBuffer() for each tuple produced by the scan. Since ReadBuffer() is
      expensive, this is a perf. win
    
    - implement dead tuple killing for GiST indexes (which is easy to do, now
      that we keep a pin on the current scan page). Now all the builtin indexes
      implement dead tuple killing.
    
    - cleanup a lot of ugly code in GiST
    eda6dd32
    History
    Name Last commit Last update
    ..