Re: mxid_score can become Infinity in pg_stat_autovacuum_scores

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: mxid_score can become Infinity in pg_stat_autovacuum_scores
Date: 2026-06-16 14:38:24
Message-ID: ajFf4IAHnk2VWpIF@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 15, 2026 at 03:26:59PM -0500, Sami Imseih wrote:
> I do think we need to mention in the docs also about this caveat
> in scoring, so users of pg_stat_autovacuum_scores are not surprised.
> As member space usage grows between 2 billion and 4 billion, the
> score ramps up gradually, but once members reach 4 billion the effective freeze
> max age drops to 0 and the score jumps to mxid_age itself,
> which could be in the hundreds of millions.

I'm -0.2 for documenting this case. I understand that users might be
confused about the results in such extreme situations, but I worry more
about users being confused by the excruciating detail of the documentation.
The existing docs are already quite complex, but I did spent a lot of time
trying to find the right balance of detail and accessibility when
committing. There are certainly other rare corner cases in which the
existing docs aren't telling the full story, and I don't think adding more
prose is really going to help.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-06-16 14:38:53 Re: Direction for test frameworks: Perl TAP vs. Python/pytest
Previous Message Robert Haas 2026-06-16 14:34:37 Re: use of SPI by postgresImportForeignStatistics