Re: Propagate XLogFindNextRecord error to callers - Mailing list pgsql-hackers

From Anthonin Bonnefoy
Subject Re: Propagate XLogFindNextRecord error to callers
Date
Msg-id CAO6_Xqqd316HhigkBsE-rC8oVsAprc_mVh5Z312D+aUOzW-5Jg@mail.gmail.com
Whole thread
In response to Re: Propagate XLogFindNextRecord error to callers  (Mircea Cadariu <cadariu.mircea@gmail.com>)
List pgsql-hackers
On Tue, Feb 3, 2026 at 5:05 PM Mircea Cadariu <cadariu.mircea@gmail.com> wrote:
> I've picked up the review for your patch.

Thanks for picking it!

> Attached is a failing test that reproduces the issue. Have I got it
> right? We can consider using it to validate your patch then.

Yeah, that's the gist of it. However, the test you've written will
only work on little endian architectures. Also, I think the xlog page
header size won't have the 4 bytes padding on 32 bits systems.

I've added a similar test in 001_basic.pl, but it relies on copying an
existing WAL file and setting the WAL magic to 0000. This way, the
result will be the same independent of the endianness and memory
padding.

Regards,
Anthonin Bonnefoy

Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Fix a bug in extension_file_exists()
Next
From: Japin Li
Date:
Subject: Re: Propagate XLogFindNextRecord error to callers