Re: mxid_score can become Infinity in pg_stat_autovacuum_scores - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: mxid_score can become Infinity in pg_stat_autovacuum_scores
Date
Msg-id CALj2ACUdSyn9JXqNdJLQRA8=vDR3on+fuSrq0oXRab0MjH6t-A@mail.gmail.com
Whole thread
In response to Re: mxid_score can become Infinity in pg_stat_autovacuum_scores  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: mxid_score can become Infinity in pg_stat_autovacuum_scores
List pgsql-hackers
Hi,

On Wed, Jun 17, 2026 at 9:18 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> 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?

+       of multixact member entries created exceeds approximately 2 billion

Although 2 billion is an internal threshold that may change to a
configurable parameter in the future depending on the workload and
disk space (per commit bd8d9c9bdf), I'm fine keeping it as is.

Attached v2 patch LGTM.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: mxid_score can become Infinity in pg_stat_autovacuum_scores
Next
From: surya poondla
Date:
Subject: Re: Handle concurrent drop when doing whole database vacuum