Re: Eagerly scan all-visible pages to amortize aggressive vacuum - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Date
Msg-id CA+TgmoaA4_GdWbYWdFdUkAMcWBXQnctzBEpQDa8EvSEpOLUFGQ@mail.gmail.com
Whole thread Raw
In response to Re: Eagerly scan all-visible pages to amortize aggressive vacuum  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Feb 3, 2025 at 9:09 PM Andres Freund <andres@anarazel.de> wrote:
> > +     <varlistentry id="guc-vacuum-max-eager-freeze-failure-rate" xreflabel="vacuum_max_eager_freeze_failure_rate">
> > +      <term><varname>vacuum_max_eager_freeze_failure_rate</varname> (<type>floating point</type>)
> > +      <indexterm>
> > +       <primary><varname>vacuum_max_eager_freeze_failure_rate</varname> configuration parameter</primary>
> > +      </indexterm>
> > +      </term>
> > +      <listitem>
> > +       <para>
> > +        Specifies the maximum fraction of pages that
> > +        <command>VACUUM</command> may scan and <emphasis>fail</emphasis> to set
> > +        all-frozen in the visibility map before disabling eager scanning. A
> > +        value of <literal>0</literal> disables eager scanning altogether. The
> > +        default is <literal>0.03</literal> (3%).
> > +       </para>
>
> Fraction of what?

"pages", according to the text.

I'm not really sure what you think is wrong with this. There may be an
even better way to explain this but this doesn't seem bad to me.

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



pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: RFC: Packing the buffer lookup table
Next
From: Robert Haas
Date:
Subject: Re: Orphaned users in PG16 and above can only be managed by Superusers