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

bootstrap.c

Blame
    • Noah Misch's avatar
      402da705
      Initialize random() in bootstrap/stand-alone postgres and in initdb. · 402da705
      Noah Misch authored
      This removes a difference between the standard IsUnderPostmaster
      execution environment and that of --boot and --single.  In a stand-alone
      backend, "SELECT random()" always started at the same seed.
      
      On a system capable of using posix shared memory, initdb could still
      conclude "selecting dynamic shared memory implementation ... sysv".
      Crashed --boot or --single postgres processes orphaned shared memory
      objects having names that collided with the not-actually-random names
      that initdb probed.  The sysv fallback appeared after ten crashes of
      --boot or --single postgres.  Since --boot and --single are rare in
      production use, systems used for PostgreSQL development are the
      principal candidate to notice this symptom.
      
      Back-patch to 9.3 (all supported versions).  PostgreSQL 9.4 introduced
      dynamic shared memory, but 9.3 does share the "SELECT random()" problem.
      
      Reviewed by Tom Lane and Kyotaro HORIGUCHI.
      
      Discussion: https://postgr.es/m/20180915221546.GA3159382@rfd.leadboat.com
      402da705
      History
      Initialize random() in bootstrap/stand-alone postgres and in initdb.
      Noah Misch authored
      This removes a difference between the standard IsUnderPostmaster
      execution environment and that of --boot and --single.  In a stand-alone
      backend, "SELECT random()" always started at the same seed.
      
      On a system capable of using posix shared memory, initdb could still
      conclude "selecting dynamic shared memory implementation ... sysv".
      Crashed --boot or --single postgres processes orphaned shared memory
      objects having names that collided with the not-actually-random names
      that initdb probed.  The sysv fallback appeared after ten crashes of
      --boot or --single postgres.  Since --boot and --single are rare in
      production use, systems used for PostgreSQL development are the
      principal candidate to notice this symptom.
      
      Back-patch to 9.3 (all supported versions).  PostgreSQL 9.4 introduced
      dynamic shared memory, but 9.3 does share the "SELECT random()" problem.
      
      Reviewed by Tom Lane and Kyotaro HORIGUCHI.
      
      Discussion: https://postgr.es/m/20180915221546.GA3159382@rfd.leadboat.com