From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: remove pg_standby? |
Date: | 2015-03-02 09:53:03 |
Message-ID: | CAHGQGwEE_8vvpQk0ex6Qa_aXt-OSJ7OdZjX4uM_FtqKfxq5SbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Feb 28, 2015 at 5:00 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 11/10/2014 10:54 AM, Magnus Hagander wrote:
>> On Mon, Nov 10, 2014 at 7:48 PM, Heikki Linnakangas
>> <hlinnakangas(at)vmware(dot)com> wrote:
>>> pg_standby is more configurable than the built-in standby_mode=on. You can
>>> set the sleep time, for example, while standby_mode=on uses a hard-coded
>>> delay of 5 s. And pg_standby has a configurable maximum wait time. And as
>>> Fujii pointed out, the built-in system will print an annoying message to the
>>> log every time it attempts to restore a file. Nevertheless, 99% of users
>>> would probably be happy with the built-in thing.
>>
>> As long as pg_standby has features that are actually useful and that
>> are not in the built-in system, we shouldn't remove it. We should,
>> however, try to fix those in the main system so we can get rid of it
>> after that :)
>
> As of current 9.5, we have configurable retries and standby delay in
> mainstream. Is there some reason we still need pg_standby?
Yes, it's not easy to perform "fast failover" without pg_standby for now.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2015-03-02 10:13:17 | Re: [REVIEW] Re: Compression of full-page-writes |
Previous Message | Haribabu Kommi | 2015-03-02 06:36:18 | Re: Providing catalog view to pg_hba.conf file - Patch submission |