Re: Hot standby fails if any backend crashes

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Hot standby fails if any backend crashes
Дата
Msg-id CA+U5nMJ+S5X-Z6dsGsO_y6m_9LaJbuD98ed10Bj7LgRmUJjO8g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Hot standby fails if any backend crashes  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Fri, Feb 3, 2012 at 4:48 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I think saner behavior might only require this change:
>
>            /*
>             * Any unexpected exit (including FATAL exit) of the startup
>             * process is treated as a crash, except that we don't want to
>             * reinitialize.
>             */
>            if (!EXIT_STATUS_0(exitstatus))
>            {
> -               RecoveryError = true;
> +               if (!FatalError)
> +                   RecoveryError = true;
>                HandleChildCrash(pid, exitstatus,
>                                 _("startup process"));
>                continue;
>            }
>
> plus suitable comment adjustments of course.  Haven't tested this yet
> though.

Looks good, will test.

> It's a bit disturbing that nobody has reported this from the field yet.
> Seems to imply that hot standby isn't being used much.

There are many people I know using it in production for more than a year now.

Either they haven't seen it or they haven't reported it to us.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


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

Предыдущее
От: Kohei KaiGai
Дата:
Сообщение: Re: [v9.2] sepgsql's DROP Permission checks
Следующее
От: Greg Smith
Дата:
Сообщение: Re: basic pgbench runs with various performance-related patches