On Mon, Oct 27, 2025 at 12:47:15PM -0500, Sami Imseih wrote:
> 1/ Should we add documentation explaining this prioritization behavior in [0]?
>
> I wrote a sql that returns the tables and scores, which I found was
> useful when I was testing this out, so having the actually rules spelled out
> in docs will actually be super useful.
Can you elaborate on how it would be useful? I'd be open to adding a short
note that autovacuum attempts to prioritize the tables in a smart way, but
I'm not sure I see the value of documenting every detail. I also don't
want to add too much friction to future changes to the prioritization
logic.
> If we don't want to go that much in depth, at minimum the docs should say:
>
> "Autovacuum prioritizes tables based on how far they exceed their thresholds
> or if they are approaching wraparound limits." so a DBA can understand
> this behavior.
Yeah, I would probably choose to keep it relatively vague like this.
> * The score is calculated as the maximum of the ratios of each of the table's
> * relevant values to its threshold. For example, if the number of inserted
> * tuples is 100, and the insert threshold for the table is 80, the insert
> * score is 1.25.
>
> Should we consider clamping down on the score when
> reltuples = -1, otherwise the scores for such tables ( new tables
> with a large amount of ingested data ) will be over-inflated? Perhaps,
> if reltuples = -1 ( # of reltuples not known ), then give a score of .5,
> so we are not over-prioritizing but not pushing down to the bottom?
I'm not sure it's worth expending too much energy to deal with this. In
the worst case, the table will be given an arbitrarily high priority the
first time it is vacuumed, but AFAICT that's it. But that's already the
case, as the thresholds will be artificially low before the first
VACUUM/ANALYZE.
--
nathan
