Re: Eagerly scan all-visible pages to amortize aggressive vacuum

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Treat <rob(at)xzilla(dot)net>
Subject: Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Date: 2025-01-15 19:35:52
Message-ID: CAB-JLwYdsP7B8+rp09tbc4_6Rq_rAdj6GZyU7BZkA0QA+aghEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> On 14.01.2025 22:51, Melanie Plageman wrote:
>

There is a typo on committed vacuumlazy.c file
* If the TID store fills up in phase I, vacuum suspends phase I, proceeds
to
* phases II and II, cleaning up the dead tuples referenced in the current
TID
* store. This empties the TID store resumes phase I.

Probably you meant phases II and III

regards
Marcos

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-01-15 19:37:58 Re: Virtual generated columns
Previous Message Thomas Munro 2025-01-15 19:21:08 Re: convert libpgport's pqsignal() to a void function