Re: Keepalive for max_standby_delay
От | Heikki Linnakangas |
---|---|
Тема | Re: Keepalive for max_standby_delay |
Дата | |
Msg-id | 4C2F8CDC.5040702@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Keepalive for max_standby_delay (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Keepalive for max_standby_delay
|
Список | pgsql-hackers |
On 03/07/10 18:32, Tom Lane wrote: > 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. Do you mean when using something like pg_standby, which does the waiting itself? > 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. With pg_standby etc. you use standby_mode=off. Same with traditional archive recovery. In standby mode, it's on. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: