| 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-17 16:18:39 |
| Message-ID: | ajLI39rH9-I-PmMR@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-fix-division-by-zero-when-calculating-autovacuum-.patch | text/plain | 3.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-06-17 17:29:09 | Re: [PATCH] Doc: document standard_conforming_strings dump/restore incompatibility |
| Previous Message | Bharath Rupireddy | 2026-06-17 16:18:14 | Re: [PATCH] Improving index selection for logical replication apply with replica identity full |