Re: Propagate XLogFindNextRecord error to callers

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Japin Li <japinli(at)hotmail(dot)com>
Subject: Re: Propagate XLogFindNextRecord error to callers
Date: 2026-03-23 12:00:00
Message-ID: CAHGQGwGxg40aD5Lp3j4EvVzNf8=hpc8Jq_ueUBpzro_A0RSLVA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 23, 2026 at 5:15 PM Anthonin Bonnefoy
<anthonin(dot)bonnefoy(at)datadoghq(dot)com> wrote:
> > +# Wrong WAL version. We copy an existing wal file and set the
> > +# page's magic value to 0000.
> >
> > Would it be better to describe the purpose of this test at the top?
> > For example:
> >
> > # Test that pg_waldump reports a detailed error message when dumping
> > # a WAL file with an invalid magic number (0000).
> > {
> > # The broken WAL file is created by copying a valid WAL file and
> > # overwriting its magic number with 0000.
> > my $broken_wal_dir = PostgreSQL::Test::Utils::tempdir_short();
>
> Sounds good, I've updated the patch.

Thanks for updating the patch!

It looks like the first part of the comment above wasn't included,
so I've added it. I also made a few cosmetic changes and updated
the commit message. Attached is the updated version of the patch.

Unless there are objections, I'll commit this version.

Regards,

--
Fujii Masao

Attachment Content-Type Size
v8-0001-Report-detailed-errors-from-XLogFindNextRecord-fa.patch application/octet-stream 9.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-03-23 12:00:34 Re: Adding REPACK [concurrently]
Previous Message Peter Eisentraut 2026-03-23 11:57:43 Re: Trying out <stdatomic.h>