Re: Fixing a couple of buglets in how VACUUM sets visibility map bits
От | Peter Geoghegan |
---|---|
Тема | Re: Fixing a couple of buglets in how VACUUM sets visibility map bits |
Дата | |
Msg-id | CAH2-WzkWON4OCf9x7-eEUSrBm2y1BfDxhBOc4h+x2R4T_9c3aA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Fixing a couple of buglets in how VACUUM sets visibility map bits (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: Fixing a couple of buglets in how VACUUM sets visibility map bits
|
Список | pgsql-hackers |
On Tue, Jan 10, 2023 at 11:47 AM Peter Geoghegan <pg@bowt.ie> wrote: > In summary, I think that there is currently no way that we can have > the VM (or the PD_ALL_VISIBLE flag) concurrently unset, while leaving > the page all_frozen. It can happen and leave the page all_visible, but > not all_frozen, due to these very fine details. (Assuming I haven't > missed another path to the problem with aborted Multis or something, > but looks like I haven't.) Actually, FreezeMultiXactId() can fully remove an xmax that has some member XIDs >= OldestXmin, provided FRM_NOOP processing isn't possible, at least when no individual member is still running. Doesn't have to involve transaction aborts at all. Let me go try to break it that way... -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: