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: Bruce Momjian <bruce@momjian.us>, Simon Riggs <simon@2ndQuadrant.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2011-11-08T19:39:12Z

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

> configuration data somewhere else, but we really need to be able to tell
> the difference between "starting PITR", "continuing PITR after a
> mid-recovery crash", and "finished PITR, up and running normally".
> A GUC is not a good way to do that.

Does a GUC make sense to you for how to handle standby/master for
replication?

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