Re: Add pg_stat_autovacuum_priority

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, 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>, tndrwang(at)gmail(dot)com
Subject: Re: Add pg_stat_autovacuum_priority
Date: 2026-04-08 21:23:45
Message-ID: adbHYQMZ0pHQttWa@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 08, 2026 at 04:40:03PM -0400, Andres Freund wrote:
> Note that the whole cached state does automatically get reset at the end of
> the transaction (AtEOXact_PgStat()->pgstat_clear_snapshot()), just like it did
> before the shmem stats stuff.

I see a lot of memory used for the pgStatEntryRefHash table, too (e.g., ~16
MB for 100K tables). What's interesting is that I cannot reproduce similar
usage with views like pg_stat_all_tables. If memory was not a concern, I
think the "bool *may_free" idea would be fine. But assuming it is, we will
probably need to do something more creative.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-04-08 21:25:02 Re: DEREF_AFTER_NULL: src/common/jsonapi.c:2529
Previous Message Nathan Bossart 2026-04-08 21:19:57 Re: Add pg_stat_autovacuum_priority