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

commands

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    in favor of looking at the flat file copy of pg_database during backend
    startup.  This should finally eliminate the various corner cases in which
    backend startup fails unexpectedly because it isn't able to distinguish
    live and dead tuples in pg_database.  Simplify locking on pg_database
    to be similar to the rules used with pg_shadow and pg_group, and eliminate
    FlushRelationBuffers operations that were used only to reduce the odds
    of failure of GetRawDatabaseInfo.
    initdb forced due to addition of a trigger to pg_database.
    0fc4ecf9
    History
    Name Last commit Last update
    ..