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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Melanie Plageman <melanieplageman(at)gmail(dot)com>
Cc: Robert Treat <rob(at)xzilla(dot)net>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, 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>
Subject: Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Date: 2025-01-23 18:31:05
Message-ID: CA+TgmoZ1ofYGvr6=YL+TX52eqoBQOHDj9s8G1_KmvqgXhDtyMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 22, 2025 at 5:48 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
> Thanks! Attached v9 incorporates all your suggested changes.

I'm not exactly sure what to do about it, but I feel like the
documentation of vacuum_eager_scan_max_fails is going to be
incomprehensible to someone who doesn't already have a deep knowledge
of how this patch works.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2025-01-23 18:38:37 Re: "postmaster became multithreaded" is reachable
Previous Message Laurenz Albe 2025-01-23 18:28:19 Re: Wrong security context for deferred triggers?