Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
| От | Kirill Reshke |
|---|---|
| Тема | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |
| Дата | |
| Msg-id | CALdSSPg+B8RTzTXhJvCcKJBqgzhPZkq0E2oqxQdv74ZNZOMVzg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) (Melanie Plageman <melanieplageman@gmail.com>) |
| Ответы |
Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
|
| Список | pgsql-hackers |
On Tue, 18 Nov 2025 at 04:07, Melanie Plageman <melanieplageman@gmail.com> wrote: > > Attached v20 has general cleanup, changes to the table/index AM > callbacks detailed below, and it moves the > heap_page_prune_and_freeze() refactoring commit down the stack to > 0004. > > 0001 - 0003 are fairly trivial cleanup patches. I think they are ready > to commit, so if I don't hear any objections in the next few days, > I'll go ahead and commit them. > Hi! I looked up these 0002-0003 patches once again, LGTM. In particular, I think 0002 & 0003 makes VM bits management more simple. My only review comment is about 0003: Should we make frz_conflict_horizon not a heap_page_will_freeze's argument but rather just another field of PruneState struct? If i'm not mistaken, 'frz_conflict_horizon' fits good to be a part of pruning state -- Best regards, Kirill Reshke
В списке pgsql-hackers по дате отправления: