From: | Robert Treat <rob(at)xzilla(dot)net> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Joshua Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: unite recovery.conf and postgresql.conf |
Date: | 2011-11-01 18:12:28 |
Message-ID: | CAJSLCQ3Htao0+JfCv2yJZgeqPGciVs5oBdDOwhRiehZaOA_dBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 1, 2011 at 1:34 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Tue, Nov 1, 2011 at 5:11 PM, Joshua Berkus <josh(at)agliodbs(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 2011-11-01 18:15:41 | Re: IDLE in transaction introspection |
Previous Message | Merlin Moncure | 2011-11-01 18:10:02 | Re: Compiler branch prediction hints (was: So, is COUNT(*) fast now?) |