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

Date: 2012-05-11T10:08:36Z

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 10 May 2012 05:44, Josh Berkus <josh@agliodbs.com> wrote:
>
>> I expect to revisit config directories before the first 9.3 CF, it will
>> help multiple things I'd like to see happen.  Then we can circle back to
>> the main unification job with a fairly clear path forward from there.
>
> Yeah, let's discuss this next week.  "Easier configuration" is one
> demand I'm hearing from developers in general, and I don't think that's
> nearly as hard a feature as, say, parallel query.  We can do it.

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

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

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