Re: unite recovery.conf and postgresql.conf

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

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

Cc: pgsql-hackers@postgresql.org

Date: 2012-05-11T17:06:00Z

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

> A key requirement is to be able to drop in new config files without
> needing to $EDIT anything.

Yes, absolutely.  I want to move towards the idea that the majority of
our users never edit postgresql.conf by hand.

> OK, its possible to put in lots of includeifexists for non-existent
> files just in case you need one, but that sucks.

Yeah, seems like we need something more elegant.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com