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

From Arseniy Mukhin
Subject Re: Remove custom redundant full page write description from GIN
Date
Msg-id CAE7r3MK_qKkzb0FZ5DMukiVs8PAeFkUacWLRTXqSMhUBsDD2Fg@mail.gmail.com
Whole thread Raw
In response to Re: Remove custom redundant full page write description from GIN  (Andrey Borodin <x4mmm@yandex-team.ru>)
Responses Re: Remove custom redundant full page write description from GIN
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Thoughts on a "global" client configuration?
Next
From: David Rowley
Date:
Subject: Re: Improve docs for n_distinct_inherited