Re: unite recovery.conf and postgresql.conf

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

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

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

Date: 2011-09-24T16:14:31Z

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 24, 2011 at 9:02 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> The semantics are clear: recovery.conf is read first, then
> postgresql.conf. It's easy to implement (1 line of code) and easy to
> understand.

Eh, well, if you can implement it in one line of code, consider my
objection withdrawn.  I can't see how that would be possible, though.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company