Re: max_standby_delay considered harmful

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: max_standby_delay considered harmful
Дата
Msg-id AANLkTilnuYddIZAnD2bVCve3s_i8s6oQwGMuUSQua2RQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: max_standby_delay considered harmful  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: max_standby_delay considered harmful  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers
On Thu, May 13, 2010 at 1:12 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 5/12/10 8:07 PM, Robert Haas wrote:
>> I think that would be a good thing to check (it'll confirm whether
>> this is the same bug), but I'm not convinced we should actually fix it
>> that way.  Prior to 8.4, we handled a smart shutdown during recovery
>> at the conclusion of recovery, just prior to entering normal running.
>> I'm wondering if we shouldn't revert to that behavior in both 8.4 and
>> HEAD.
>
> This would be OK as long as we document it well.  We patched the
> shutdown the way we did specifically because Fujii thought it would be
> an easy fix; if it's complicated, we should revert it and document the
> issue for DBAs.

I don't understand this comment.

> Oh, and to confirm: the same issue exists, and has always existed, with
> Warm Standby.

That's what I was thinking, but I hadn't gotten around to testing it.
Thanks for the confirmation.

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


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Generating Lots of PKs with nextval(): A Feature Proposal
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: max_standby_delay considered harmful