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

Date: 2011-10-31T19:19:50Z

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 Mon, Oct 31, 2011 at 7:05 PM, Josh Berkus <josh@agliodbs.com> wrote:

> If it's possible to run a replica without having a recovery.conf file,
> then I'm fine with your solution.  If it's not, then I find your
> solution not to be a solution at all.

Then you are fine with the solution - not mine alone, just the sum of
everybody's inputs.

So we can teach the new way, while supporting the old way a while longer.

> Sure.  recovery.conf worked fine for PITR.  We've just overextended it
> for other purposes.

Agreed.

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