Re: Add pg_stat_autovacuum_priority

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, satyanarlapuram(at)gmail(dot)com, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add pg_stat_autovacuum_priority
Date: 2026-04-08 17:00:00
Message-ID: 5684f479-858e-4c5d-b8f5-bcf05de1f909@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Nathan,

07.04.2026 00:58, Nathan Bossart wrote:
> Committed after some more editorialization.

Please look at a new anomaly, I and SQLsmith have discovered:
SELECT (SELECT score FROM pg_stat_get_autovacuum_scores() LIMIT 1),
    (SELECT score FROM pg_stat_get_autovacuum_scores() LIMIT 1);
ERROR:  detected double pfree in PgStat Snapshot 0x5f6fa4d95d50

Best regards,
Alexander

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2026-04-08 17:01:15 Re: Add errdetail() with PID and UID about source of termination signal
Previous Message Ilia Evdokimov 2026-04-08 16:48:49 Re: Hash-based MCV matching for large IN-lists