Re: unite recovery.conf and postgresql.conf

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org

Date: 2011-09-20T19:57:53Z

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

> The point I'm trying to make is that it seems like this discussion is
> getting driven entirely by the standby case, without remembering that
> recovery.conf was originally designed for, and is still used in,
> a significantly different use-case.  Maybe we had better take two
> steps back and think about the implications for the archive-recovery
> case.

I think we should take that into consideration, sure.  But it should not
be in the driver's seat for things like nomenclature.  Far more people
use replication than use PITR.

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