Re: BUG #19867: pg_verifybackup accepts out-of-range Timeline in backup manifest

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: imchifan(at)mail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19867: pg_verifybackup accepts out-of-range Timeline in backup manifest
Date: 2026-11-11 11:02:07
Message-ID: 041B43B3-FD58-4663-B221-55A71FEC2858@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 11 Nov 2026, at 06:46, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:

> sed -i '0,/"Timeline": [0-9][0-9]*/s//"Timeline": 4294967297/'

> "Timeline": 4294967297
> pg_verifybackup: error: manifest checksum mismatch

This seems to have been working as intended no? You corrupted the manifest and
the checksum verification failed due to the corruption. Tightening the parsing
in the absence of issues doesn't strike me as high on the prioritization list
right now.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Reshke 2026-11-11 11:03:10 Re: BUG #19861: Self-join elimination drops a VOLATILE predicate and changes the query result
Previous Message PG Bug reporting form 2026-11-11 10:17:19 BUG #19874: CREATE SCHEMA view binds same-named table in pg_temp and fails