Postgres Pro
Downloads
Home   >   mailing lists

Re: Enforcing that all WAL has been replayed after restoring from backup - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Enforcing that all WAL has been replayed after restoring from backup
Date
Msg-id 1312903147-sup-1603@alvh.no-ip.org
Whole thread Raw
In response to Enforcing that all WAL has been replayed after restoring from backup  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Enforcing that all WAL has been replayed after restoring from backup
List pgsql-hackers
Tree view 
Excerpts from Heikki Linnakangas's message of mar ago 09 05:00:00 -0400 2011:

> I think this is a nice additional safeguard to have, making streamed 
> backups more robust. I'd like to add this to 9.1, but it required an 
> extra field to be added to the control file, so it would force an 
> initdb. It's probably not worth that. Or, we could sneak in the extra 
> boolean field to some currently unused pad space in the ControlFile struct.

How about making the new backup_label field optional?  If absent, assume
current behavior.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build)
Next
From: Heikki Linnakangas
Date:
Subject: Re: Enforcing that all WAL has been replayed after restoring from backup