Re: Hot Standby startup with overflowed snapshots

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Hot Standby startup with overflowed snapshots
Дата
Msg-id CA+TgmoZpxRxrPWxp6c1jScxG66tEBKXxUuLxSRxUV3Oao-xyqQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Hot Standby startup with overflowed snapshots  (Simon Riggs <simon@2ndQuadrant.com>)
Список pgsql-hackers
On Thu, Oct 27, 2011 at 6:55 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> It seems cheap to add in a call to LogStandbySnapshot() after each
> call to pg_stop_backup().
>
> Does anyone think this case is worth adding code for? Seems like one
> more thing to break.

Why at that particular time?

It would maybe nice if the master could notice when it has a plausible
(non-overflowed) snapshot and log it then.  But that might be more
code than the problem is worth.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_upgrade if 'postgres' database is dropped
Следующее
От: pasman pasmański
Дата:
Сообщение: Include commit identifier in version() function