| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <cb(at)df7cb(dot)de>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add shutdown_at_recovery_target option to recovery.conf |
| Date: | 2014-11-27 02:30:15 |
| Message-ID: | CAB7nPqSejzo-hAZ9t4i0GLF7uTVMJkYJbMneAXEofp038mR4OQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 26, 2014 at 7:10 PM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
> Re: Petr Jelinek 2014-11-25 <5474EFEA(dot)2040000(at)2ndquadrant(dot)com>
>> >Patch committed.
>>
>> Thanks!
>
> I'm a bit late to the party, but wouldn't
>
> recovery_target_action = ...
>
> have been a better name for this? It'd be in line with the other
> recovery_target_* parameters, and also a bit shorter than the imho
> somewhat ugly "action_at_recovery_target".
Looks like a good idea to me. Why not as well mark
pause_at_recovery_target as deprecated in the docs and remove it in,
let's say, 2 releases?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2014-11-27 03:20:12 | Re: dblink_get_connections() result for no connections |
| Previous Message | Stephen Frost | 2014-11-27 02:01:13 | Re: Add CREATE support to event triggers |