Re: Keepalive for max_standby_delay

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Keepalive for max_standby_delay
Дата
Msg-id 11126.1278171129@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Keepalive for max_standby_delay  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Keepalive for max_standby_delay  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> It would seem logical to use the same logic for archive recovery as we 
> do for streaming replication, and only set XLogReceiptTime when you have 
> to wait for a WAL segment to arrive into the archive, ie. when 
> restore_command fails.

That would not do what you want at all in the case where you're
recovering from archive --- XLogReceiptTime would never advance
at all for the duration of the recovery.

It might be useful if you knew that it was a standby-with-log-shipping
situation, but we have no way to tell the difference.

The restore_command might know the difference, though.  Is it
worth modifying its API somehow so that the command could tell us
whether to advance XLogReceiptTime?  How would we do that?
        regards, tom lane


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

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Keeping separate WAL segments for each database
Следующее
От: Tom Lane
Дата:
Сообщение: Re: reassign owned to change the ownership for op class and family