Re: doc: fix pg_stat_autovacuum_scores threshold wording - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: doc: fix pg_stat_autovacuum_scores threshold wording
Date
Msg-id 20260625.124519.465561960978243461.horikyota.ntt@gmail.com
Whole thread
In response to doc: fix pg_stat_autovacuum_scores threshold wording  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: doc: fix pg_stat_autovacuum_scores threshold wording
List pgsql-hackers
Hello,

At Thu, 25 Jun 2026 10:44:23 +0800, Chao Li <li.evan.chao@gmail.com> wrote in 
> While testing “[d7965d65f] Add rudimentary table prioritization to autovacuum”, I noticed a small doc issue.
> 
> In monitoring.sgml, it states:
> ```
>      <row>
>       <entry role="catalog_table_entry"><para role="column_definition">
>        <structfield>vacuum_score</structfield> <type>double precision</type>
>       </para>
>       <para>
>        Vacuum component score.  Scores greater than or equal to
>        <xref linkend="guc-autovacuum-vacuum-score-weight"/> indicate that
>        autovacuum would vacuum the table (unless autovacuum is disabled).
>       </para></entry>
>      </row>
> ```

If I understand this correctly, aren't the *_score_weight settings
used to prioritize candidate tables, rather than to determine whether
a table needs vacuuming or analyzing in the first place?

Regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: shveta malik
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication