Re: Enforcing that all WAL has been replayed after restoring from backup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Enforcing that all WAL has been replayed after restoring from backup
Date: 2011-08-09 16:07:14
Message-ID: 19501.1312906034@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-08-09 16:16:16 Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build)
Previous Message Andrew Dunstan 2011-08-09 15:43:06 Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https