Re: Requiring recovery.signal or standby.signal when recovering with a backup_label

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: michael(at)paquier(dot)xyz
Cc: robertmhaas(at)gmail(dot)com, david(at)pgmasters(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org, zxwsbg12138(at)gmail(dot)com, david(dot)zhang(at)highgo(dot)ca, andres(at)anarazel(dot)de
Subject: Re: Requiring recovery.signal or standby.signal when recovering with a backup_label
Date: 2023-11-02 02:03:35
Message-ID: 20231102.110335.1808777803530400869.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Wed, 1 Nov 2023 08:39:17 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in
> See in StartupXLOG(), around the comment "complain if we did not roll
> forward far enough to reach". This complains if archive recovery has
> been requested *or* if we retrieved a backup end LSN from the
> backup_label.

Please note that backupStartPoint is not reset even when reaching the
backup end point during crash recovery. If backup_label enforces
archive recovery, I think this point won't be an issue as you
mentioned. For the record, my earlier proposal aimed to detect
reaching the end point even during crash recovery.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Xing Guo 2023-11-02 02:09:27 Re: Don't pass NULL pointer to strcmp().
Previous Message Tom Lane 2023-11-02 01:57:18 Re: Don't pass NULL pointer to strcmp().