Re: mxid_score can become Infinity in pg_stat_autovacuum_scores

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-06-17T16:18:39Z
Lists: pgsql-hackers

Attachments

On Tue, Jun 16, 2026 at 11:21:57AM -0500, Sami Imseih wrote:
> I think this particular scenario is very clear to explain just like how
> we explain the failsafe scenario. Also, the suggested docs in the view
> link to the already existing detailed explanation of this behavior.
> 
> More generally, I think anytime there is a drastic change in a score,
> like jumping from a gradually ramping value around 1.x to suddenly
> hundreds of millions, that's something worth calling out in the docs.
> Users monitoring pg_stat_autovacuum_scores will notice that jump and want
> to understand why it happened.

Okay.  I fiddled with the patch a bit and came up with the attached.  WDYT?

-- 
nathan

Commits

  1. Avoid division-by-zero when calculating autovacuum MXID score.

  2. Widen MultiXactOffset to 64 bits