Re: unite recovery.conf and postgresql.conf
Josh Berkus <josh@agliodbs.com>
From: Josh Berkus <josh@agliodbs.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2011-09-20T17:13:00Z
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 9/20/11 10:09 AM, Robert Haas wrote: > I like the idea of some kind of sentinel file that tells the server to > start up in recovery mode. But instead of having the user remove it > to cause a promotion, I think the server should remove it when it does > promote. That's more like what we've done in the past, and it ties in > very nicely with what pg_ctl promote already does. Yes, I agree that that is a superior approach. And then we could keep the trigger_file configuration parameter for backwards compatibility, with intent to depreciate it after a couple more Postgres versions. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com