Re: unite recovery.conf and postgresql.conf

Magnus Hagander <magnus@hagander.net>

From: Magnus Hagander <magnus@hagander.net>

To: Greg Stark <stark@mit.edu>

Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org

Date: 2011-09-10T05:59:41Z

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 Sat, Sep 10, 2011 at 01:07, Greg Stark <stark@mit.edu> wrote:
> On Fri, Sep 9, 2011 at 6:40 PM, Josh Berkus <josh@agliodbs.com> wrote:
>> I'm in favor of this.  People are sufficiently confused by the existing
>> behavior that we're not going to confuse them further by changing it.
>>
>
> Fwiw as someone who *was* confused previously, it now makes perfect
> sense to me. "We have postgres.conf which always applies and then
> recovery.conf which can have all the same options but they only apply
> during recover". That's much clearer than "we have two configuration

But it only means that for *some* options. Which certainly doesn't
reduce confusion.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/