| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: unite recovery.conf and postgresql.conf |
| Date: | 2011-09-20 17:13:00 |
| Message-ID: | 4E78C99C.5010008@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-09-20 17:25:59 | Re: File not found error on creating collation |
| Previous Message | Robert Haas | 2011-09-20 17:09:29 | Re: unite recovery.conf and postgresql.conf |