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

xlog.c

Blame
    • Heikki Linnakangas's avatar
      06f82b29
      Write an end-of-backup WAL record at pg_stop_backup(), and wait for it at · 06f82b29
      Heikki Linnakangas authored
      recovery instead of reading the backup history file. This is more robust,
      as it stops you from prematurely starting up an inconsisten cluster if the
      backup history file is lost for some reason, or if the base backup was
      never finished with pg_stop_backup().
      
      This also paves the way for a simpler streaming replication patch, which
      doesn't need to care about backup history files anymore.
      
      The backup history file is still created and archived as before, but it's
      not used by the system anymore. It's just for informational purposes now.
      
      Bump PG_CONTROL_VERSION as the location of the backup startpoint is now
      written to a new field in pg_control, and catversion because initdb is
      required
      
      Original patch by Fujii Masao per Simon's idea, with further fixes by me.
      06f82b29
      History
      Write an end-of-backup WAL record at pg_stop_backup(), and wait for it at
      Heikki Linnakangas authored
      recovery instead of reading the backup history file. This is more robust,
      as it stops you from prematurely starting up an inconsisten cluster if the
      backup history file is lost for some reason, or if the base backup was
      never finished with pg_stop_backup().
      
      This also paves the way for a simpler streaming replication patch, which
      doesn't need to care about backup history files anymore.
      
      The backup history file is still created and archived as before, but it's
      not used by the system anymore. It's just for informational purposes now.
      
      Bump PG_CONTROL_VERSION as the location of the backup startpoint is now
      written to a new field in pg_control, and catversion because initdb is
      required
      
      Original patch by Fujii Masao per Simon's idea, with further fixes by me.