Re: unite recovery.conf and postgresql.conf

Josh Berkus <josh@agliodbs.com>

From: Josh Berkus <josh@agliodbs.com>

To: pgsql-hackers@postgresql.org

Date: 2011-12-02T20:49:17Z

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

All:

*ping*

Trying to restart this discussion, since the feature bogged down on
spec.  We have consensus that we need to change how replication mode is
mangaged; surely we can reach consensus on how to change it?

On 11/8/11 11:39 AM, Josh Berkus wrote:
> 
>> 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