Re: pg_veryfybackup can fail with a valid backup for TLI > 1

At Fri, 20 Aug 2021 16:23:56 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in
> On Fri, Aug 20, 2021 at 03:33:37PM +0900, Kyotaro Horiguchi wrote:
> > That's looks like a domino falling. I had the following result, which
> > looks fine.
> >
> > "WAL-Ranges": [
> > { "Timeline": 6, "Start-LSN": "0/630C7E8", "End-LSN": "0/630C850" },
> > { "Timeline": 5, "Start-LSN": "0/630C780", "End-LSN": "0/630C7E8" },
> > { "Timeline": 4, "Start-LSN": "0/630C718", "End-LSN": "0/630C780" },
> > { "Timeline": 3, "Start-LSN": "0/630C6B0", "End-LSN": "0/630C718" },
> > { "Timeline": 2, "Start-LSN": "0/5000028", "End-LSN": "0/630C6B0" }
> > ],
> >
> > 00000006.history:
> > 1 0/173F268 no recovery target specified
> > 2 0/630C6B0 no recovery target specified
> > 3 0/630C718 no recovery target specified
> > 4 0/630C780 no recovery target specified
> > 5 0/630C7E8 no recovery target specified
>
> And your backup_label shows 0/5000028 as start LSN for the backup,
> right? I see the same result.

Yes, backup_label looks correct.

backup_label (extract):
START WAL LOCATION: 0/5000028 (file 000000020000000000000005)
CHECKPOINT LOCATION: 0/5000060
START TIMELINE: 2

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center