Re: pg_veryfybackup can fail with a valid backup for TLI > 1 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: pg_veryfybackup can fail with a valid backup for TLI > 1
Date
Msg-id YR9YjIiOK9pFQhQO@paquier.xyz
Whole thread Raw
In response to Re: pg_veryfybackup can fail with a valid backup for TLI > 1  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: pg_veryfybackup can fail with a valid backup for TLI > 1
List pgsql-hackers
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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Alexander Pyhalov
Date:
Subject: Re: Push down time-related SQLValue functions to foreign server
Next
From: Alexander Pyhalov
Date:
Subject: Re: Push down time-related SQLValue functions to foreign server