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
    it is trying to build a relcache entry for.  This is an oversight in my 8.2
    patch that tried to ensure we always took a lock on a relation before trying
    to build its relcache entry.  The implication is that if someone committed a
    reindex of a critical system index at about the same time that some other
    backend were starting up without a valid pg_internal.init file, the second one
    might PANIC due to not seeing any valid version of the index's pg_class row.
    Improbable case, but definitely not impossible.
    0f45d1eb
    History
    Name Last commit Last update