Re: Remove custom redundant full page write description from GIN
| От | Arseniy Mukhin | 
|---|---|
| Тема | Re: Remove custom redundant full page write description from GIN | 
| Дата | |
| Msg-id | CAE7r3MK_qKkzb0FZ5DMukiVs8PAeFkUacWLRTXqSMhUBsDD2Fg@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Re: Remove custom redundant full page write description from GIN (Andrey Borodin <x4mmm@yandex-team.ru>) | 
| Ответы | 
                	
            		Re: Remove custom redundant full page write description from GIN
            		
            		 | 
		
| Список | 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 по дате отправления: