Re: HOT line pointer bloat and PageRepairFragmentation
| От | Zeugswetter Andreas ADI SD |
|---|---|
| Тема | Re: HOT line pointer bloat and PageRepairFragmentation |
| Дата | |
| Msg-id | E1539E0ED7043848906A8FF995BDA579025C5D36@m0143.s-mxs.net обсуждение исходный текст |
| Ответ на | Re: HOT line pointer bloat and PageRepairFragmentation ("Pavan Deolasee" <pavan.deolasee@gmail.com>) |
| Ответы |
Re: HOT line pointer bloat and PageRepairFragmentation
Re: HOT line pointer bloat and PageRepairFragmentation |
| Список | pgsql-hackers |
> The COLD updated (old) tuple would be pruned to dead line pointer > once the tuple becomes DEAD. Normally that would let us reuse the > tuple storage for other purposes. We do the same for DELETEd tuples. Oh, I thought only pruned tuples from HOT chains can produce a "redirect dead" line pointer. This looks like a problem, since we might end up with a page filled with LP_DEAD slots, that all have no visibility info and can thus not be cleaned by vacuum. Maybe PageRepairFragmentation when called from HOT should prune less aggressively. e.g. prune until a max of 1/2 the available slots are LP_DEAD, and not prune the rest. Andreas
В списке pgsql-hackers по дате отправления: