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
    index's support-function cache (in index_getprocinfo).  Since none of that
    data can change for an index that's in active use, it seems sufficient to
    treat all open indexes the same way we were treating "nailed" system indexes
    --- that is, just re-read the pg_class row and leave the rest of the relcache
    entry strictly alone.  The pg_class re-read might not be strictly necessary
    either, but since the reltablespace and relfilenode can change in normal
    operation it seems safest to do it.  (We don't support changing any of the
    other info about an index at all, at the moment.)
    
    Back-patch as far as 8.0.  It might be possible to adapt the patch to 7.4,
    but it would take more work than I care to expend for such a low-probability
    problem.  7.3 is out of luck for sure.
    ed69cf5d
    History
    Name Last commit Last update
    ..