| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for changes to recovery.conf API |
| Date: | 2016-09-06 14:11:51 |
| Message-ID: | 77122541-8ef8-89a5-b8f7-361af007cd02@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/6/16 8:07 AM, Robert Haas wrote:
> On Wed, Aug 31, 2016 at 9:45 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>> Related cleanup
>> * Promotion signal file is now called "promote.trigger" rather than
>> just "promote"
>> * Remove user configurable "trigger_file" mechanism - use
>> "promote.trigger" for all cases
>
> I'm in favor of this. I don't think that it's very hard for authors
> of backup tools to adapt to this new world, and I don't see that
> allowing configurability here does anything other than create more
> cases to worry about.
+1 from a backup tool author.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-09-06 14:17:53 | Re: Bug in VACUUM_TRUNCATE_LOCK_WAIT_INTERVAL |
| Previous Message | Simon Riggs | 2016-09-06 14:08:56 | Re: Quorum commit for multiple synchronous replication. |