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

From Simon Riggs
Subject Re: unite recovery.conf and postgresql.conf
Date
Msg-id CA+U5nMJU-KTGU=5mRbFWz8qQEUeiUZ7M3KxuPs4seQHEA6Kx6g@mail.gmail.com
Whole thread Raw
In response to Re: unite recovery.conf and postgresql.conf  (Josh Berkus <josh@agliodbs.com>)
Responses Re: unite recovery.conf and postgresql.conf
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: SET variable - Permission issues
Next
From: Dan Ports
Date:
Subject: Re: Overhead cost of Serializable Snapshot Isolation