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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-17 09:37:47
Message-ID: 4E4B8BEB.70302@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17.08.2011 12:26, Fujii Masao wrote:
> So, in master, we should change pg_controldata.c and pg_resetxlog.c for
> new pg_control field "backupEndRequired"?

Ah, good catch! Fixed.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Urbański 2011-08-17 09:40:55 Re: plpython crash
Previous Message Fujii Masao 2011-08-17 09:26:17 Re: Enforcing that all WAL has been replayed after restoring from backup