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

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: michael(at)paquier(dot)xyz
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_veryfybackup can fail with a valid backup for TLI > 1
Date: 2021-08-23 07:09:04
Message-ID: 20210823.160904.914282059172990217.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Mon, 23 Aug 2021 15:46:37 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in
> On Fri, Aug 20, 2021 at 04:47:15PM +0900, Kyotaro Horiguchi wrote:
> > Yes, backup_label looks correct.
> >
> > backup_label (extract):
> > START WAL LOCATION: 0/5000028 (file 000000020000000000000005)
> > CHECKPOINT LOCATION: 0/5000060
> > START TIMELINE: 2
>
> Okay. I have worked on that today, did more manual tests, and applied
> this fix down to 13. The cherry-pick from 14 to 13 only required a
> s/$master/$primary/ in the test, which was straight-forward. Your
> patch for 13 did that though:
> - if (starttli != entry->tli)
> + if (!XLogRecPtrIsInvalid(entry->begin))
>
> So it would have caused a failure with parent TLIs that have a correct
> begin location, but we expect the opposite. The patch for 14/HEAD had
> that right.

Mmm. Sorry for the silly mistake, and thanks for commiting this!

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-08-23 07:22:04 Re: Separate out FileSet from SharedFileSet (was Re: pgsql: pgstat: Bring up pgstat in BaseInit() to fix uninitialized use o)
Previous Message Ronan Dunklau 2021-08-23 06:58:50 Re: Proposal: More structured logging