From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | peter(dot)eisentraut(at)2ndquadrant(dot)com |
Cc: | leif(at)lako(dot)no, michael(at)paquier(dot)xyz, masao(dot)fujii(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pause recovery if pitr target not reached |
Date: | 2020-01-15 04:02:27 |
Message-ID: | 20200115.130227.658306293881882348.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
FWIW, I restate this (perhaps) more clearly.
At Wed, 15 Jan 2020 11:02:24 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> recvoery_target_* is not cleared after startup. If a server crashed
> just after the last shutdown checkpoint, any recovery_target_* setting
> prevents the server from starting regardless of its value.
recvoery_target_* is not automatically cleared after a successful
archive recovery. After that, if the server crashed just after the
last shutdown checkpoint, any recovery_target_* setting prevents the
server from starting regardless of its value.
> > LOG: database system was not properly shut down; automatic recovery in progress
> > LOG: invalid record length at 0/9000420: wanted 24, got 0
> (recovery is skipped)
> > FATAL: recovery ended before configured recovery target was reached
>
> I think we should ignore the setting while crash recovery. Targeted
> recovery mode is documented as a feature of archive recovery. Perhaps
> ArchiveRecoveryRequested is needed in the condition.
>
> > if (ArchiveRecoveryRequested &&
> > recoveryTarget != RECOVERY_TARGET_UNSET && !reachedStopPoint)
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-01-15 04:34:33 | Re: [HACKERS] Block level parallel vacuum |
Previous Message | Tom Lane | 2020-01-15 04:01:33 | Re: Complete data erasure |