Re: Remove custom redundant full page write description from GIN - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: Remove custom redundant full page write description from GIN
Date
Msg-id CALdSSPg74rdL0u1xTMrOePdfEAeX2Fd6FE_M0NFWo8iY2g0dww@mail.gmail.com
Whole thread Raw
In response to Re: Remove custom redundant full page write description from GIN  (Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>)
List pgsql-hackers

On Tue, 14 Oct 2025, 01:24 Arseniy Mukhin, <arseniy.mukhin.dev@gmail.com> wrote:
Hi,

On Fri, Oct 10, 2025 at 10:00 PM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
>
>
> > On 9 Oct 2025, at 17:33, Kirill Reshke <reshkekirill@gmail.com> wrote:
> >
> > Should we remove them, reducing overall cognitive complexity of GIN
> > internals and reducing WAL footprint?
>
> The patch does not add a single line... that's impressive :)
>
> Why not wipe ginxlogSplit entirely? Will the code be clearer with XLogRegisterData(&flags, sizeof(uint16))?
>
>

Looks like we will not be able to process old split records after
this, as 'flags' field offset was changed. So probably these fields
are for backward compatibility. Does it make sense?


Best regards,
Arseniy Mukhin

Hi! We do not need to support anything WAL related in new major version, since we do new initdb. There are couple of threads nearby that change WAL record layout or even drop them entirely, and that OK.
Also, we have WAL magic number for this purpose

pgsql-hackers by date:

Previous
From: Bryan Green
Date:
Subject: Re: [PATCH] Fix incorrect fprintf usage in log_error FRONTEND path
Next
From: Tom Lane
Date:
Subject: Re: [PING] [PATCH v2] parallel pg_restore: avoid disk seeks when jumping short distance forward