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: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2011-10-10T21:37:32Z

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 Mon, Oct 10, 2011 at 6:52 PM, Josh Berkus <josh@agliodbs.com> wrote:

>> Tatsuo/Josh/Robert also discussed how recovery.conf can be used to
>> provide parameters solely for recovery. That is difficult to do
>> without causing all downstream tools to make major changes in the ways
>> they supply parameters.
>
> Actually, this case is easily solved by an "include recovery.conf"
> parameter.  So it's a non-issue.

That is what I've suggested and yes, doing that is straightforward.

If you mean "do that in a program" if we had a problem with adding
parameters, we also have a problem adding an include.

We should avoid breaking programs which we have no reason to break.
Stability is good, change without purpose is not.

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