Re: unite recovery.conf and postgresql.conf - Mailing list pgsql-hackers

From Robert Treat
Subject Re: unite recovery.conf and postgresql.conf
Date
Msg-id CAJSLCQ3Htao0+JfCv2yJZgeqPGciVs5oBdDOwhRiehZaOA_dBw@mail.gmail.com
Whole thread Raw
In response to Re: unite recovery.conf and postgresql.conf  (Robert Treat <rob@xzilla.net>)
List pgsql-hackers
On Tue, Nov 1, 2011 at 1:34 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Tue, Nov 1, 2011 at 5:11 PM, Joshua Berkus <josh@agliodbs.com> wrote:
>
>> So, we have four potential paths regarding recovery.conf:
>>
>> 1) Break backwards compatibility entirely, and stop supporting recovery.conf as a trigger file at all.
>
> Note that is exactly what I have suggested when using "standby" mode
> from pg_ctl.
>
> But you already know that, since you said "If it's possible to run a
> replica without having a recovery.conf file,
> then I'm fine with your solution", and I already confirmed back to you
> that would be possible.
>

"It's possible to run a replica without having a recovery.conf file"
is not the same thing as "If someone makes a recovery.conf file, it
won't break my operations". AIUI, you are not supporting the latter.


Robert Treat
conjecture: xzilla.net
consulting: omniti.com


pgsql-hackers by date:

Previous
From: "Eric B. Ridge"
Date:
Subject: Re: Thoughts on "SELECT * EXCLUDING (...) FROM ..."?
Next
From: Simon Riggs
Date:
Subject: Re: unite recovery.conf and postgresql.conf