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

From Heikki Linnakangas
Subject Re: Enforcing that all WAL has been replayed after restoring from backup
Date
Msg-id 4E424DB3.7050506@enterprisedb.com
Whole thread Raw
In response to Re: Enforcing that all WAL has been replayed after restoring from backup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 09.08.2011 19:07, Tom Lane wrote:
> Heikki Linnakangas<heikki.linnakangas@enterprisedb.com>  writes:
>> On 09.08.2011 18:20, Alvaro Herrera wrote:
>>> How about making the new backup_label field optional?  If absent, assume
>>> current behavior.
>
>> That's how I actually did it in the patch. However, the problem wrt.
>> requiring initdb is not the new field in backup_label, it's the new
>> field in the control file.
>
> Yeah.  I think it's too late to be fooling with pg_control for 9.1.
> Just fix it in HEAD.

Done.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Reduced power consumption in autovacuum launcher process
Next
From: Magnus Hagander
Date:
Subject: Re: Enforcing that all WAL has been replayed after restoring from backup