| From: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
|---|---|
| To: | Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Propagate XLogFindNextRecord error to callers |
| Date: | 2026-02-09 09:21:59 |
| Message-ID: | CAO6_Xqqd316HhigkBsE-rC8oVsAprc_mVh5Z312D+aUOzW-5Jg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 3, 2026 at 5:05 PM Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| v2-0001-Propage-errormsg-to-XLogFindNextRecord-caller.patch | application/octet-stream | 9.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Japin Li | 2026-02-09 09:36:19 | Re: Propagate XLogFindNextRecord error to callers |
| Previous Message | Chao Li | 2026-02-09 09:21:17 | Fix a bug in extension_file_exists() |