Re: unite recovery.conf and postgresql.conf

Simon Riggs <simon@2ndquadrant.com>

From: Simon Riggs <simon@2ndQuadrant.com>

To: Josh Berkus <josh@agliodbs.com>

Cc: Robert Treat <rob@xzilla.net>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2011-11-01T19:12:17Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Restructure error handling in reading of postgresql.conf.
- d56b3afc0376 9.2.0 cited

On Tue, Nov 1, 2011 at 6:36 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 11/1/11 10:34 AM, Simon Riggs 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.
>
> I wasn't clear on that from the description of your proposal.  So are
> you suggesting that, if we start postgresql with "pg_ctl standby" then
> recovery.conf would not behave as a trigger file?

Yes

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