| From: | "Leif Gunnar Erlandsen" <leif(at)lako(dot)no> |
|---|---|
| To: | "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pause recovery if pitr target not reached |
| Date: | 2019-11-22 11:26:59 |
| Message-ID: | 4002ac55e08cce42b7ec3672323f60ba@lako.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com> skrev 22. november 2019 kl. 11:50:
> On 2019-11-21 13:50, Leif Gunnar Erlandsen wrote:
>
>> Pausing was choosen in the patch as pause was the expected behaivior if target was reached.
>
> Pausing is the expect behavior when the target is reached because that is the default setting of
> recovery_target_action. Your patch does not take recovery_target_action into account.
No it does not. It works well to demonstrate its purpose though.
And it might be to stop with FATAL would be more correct.
>
> -- Peter Eisentraut http://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-11-22 12:21:31 | Re: [HACKERS] WAL logging problem in 9.4.3? |
| Previous Message | Leif Gunnar Erlandsen | 2019-11-22 11:23:43 | Re: pause recovery if pitr target not reached |