Re: Backup history file should be replicated in Streaming Replication?

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Backup history file should be replicated in Streaming Replication?
Дата
Msg-id 23746.1261509721@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Backup history file should be replicated in Streaming Replication?  (Fujii Masao <masao.fujii@gmail.com>)
Список pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> On Wed, Dec 23, 2009 at 4:09 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> It's needed to find the place where the backup stopped, so it defines
>> the safe stopping point. We could easily pass that info via WAL, when
>> streaming. It doesn't actually matter until we try to failover.

> Right. And, it's also needed to cooperate with HS which begins accepting
> read-only queries after a recovery reaches that safe stopping point.

OK, so the information needed in the WAL record doesn't even include
most of what is in the history file, correct?  What you're actually
talking about is identifying a WAL position.  Maybe you'd want to
provide the backup label for identification purposes, but not much else.
In that case I concur that this is a better solution than hacking up
something to pass over the history file.
        regards, tom lane


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Backup history file should be replicated in Streaming Replication?
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Segfault from PL/Perl Returning vstring