| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Subject: | Re: recovery_target_action = pause & hot_standby = off |
| Date: | 2015-05-21 05:25:19 |
| Message-ID: | CAHGQGwGQXn7TfPUyHTBySXzjxoi3KpxXkSmf9shw2=Ywy5NoEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 16, 2015 at 7:39 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2015-03-16 07:52:20 +0000, Simon Riggs wrote:
>> On 15 March 2015 at 22:38, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>>
>> > Sorry, I don't buy this. If I have "recovery_target_action = 'pause'" in
>> > the config file, I want it to pause.
>>
>> You want it to enter a state where you cannot perform any action other
>> than shutdown?
>>
>> Why would anyone want that?
>
> You actually still could promote. But I'd be perfectly happy if postgres
> said
> ERROR: recovery_target_action = 'pause' in "%s" cannot be used without hot_standby
> DETAIL: Recovery pauses cannot be resumed without SQL level access.
> HINT: Configure hot_standby and try again.
This works for me.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2015-05-21 05:35:00 | Re: [COMMITTERS] pgsql: Add pg_audit, an auditing extension |
| Previous Message | Fujii Masao | 2015-05-21 04:57:57 | Re: recovery_target_action doesn't work for anything but shutdown |