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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Enforcing that all WAL has been replayed after restoring from backup
Дата
Msg-id 19501.1312906034@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Enforcing that all WAL has been replayed after restoring from backup  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Enforcing that all WAL has been replayed after restoring from backup  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: Enforcing that all WAL has been replayed after restoring from backup  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-hackers
Дерево обсуждения 
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.
        regards, tom lane

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: plperl crash with Debian 6 (64 bit), pl/perlu, libwww and https
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Compiler warnings with stringRelOpts (was WIP: Fast GiST index build)