| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Alex Shulgin <ash(at)commandprompt(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Turning recovery.conf into GUCs |
| Date: | 2014-12-02 18:31:51 |
| Message-ID: | 20141202183151.GP1737@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus wrote:
> On 12/02/2014 06:25 AM, Alex Shulgin wrote:
> > Whatever tricks we might employ will likely
> > be defeated by the fact that the oldschool user will fail to *include*
> > recovery.conf in the main conf file.
>
> Well, can we merge this patch and then fight out what to do for the
> transitional users as a separate patch?
You seem to be saying "I don't have any good idea how to solve this
problem now, but I will magically have one once this is committed". I'm
not sure that works very well.
In any case, the proposal upthread that we raise an error if
recovery.conf is found seems sensible enough. Users will see it and
they will adjust their stuff -- it's a one-time thing. It's not like
they switch a version forwards one week and back the following week.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-02 18:35:21 | Re: How about a option to disable autovacuum cancellation on lock conflict? |
| Previous Message | Robert Haas | 2014-12-02 18:19:12 | Re: How about a option to disable autovacuum cancellation on lock conflict? |