Re: Track skipped tables during autovacuum and autoanalyze

From: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Track skipped tables during autovacuum and autoanalyze
Date: 2026-03-26 02:25:29
Message-ID: 20260326112529.5ea04c6f5e91e490b07c0e57@sraoss.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 26 Mar 2026 10:31:19 +0900
Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Thu, Mar 26, 2026 at 10:18:39AM +0900, Yugo Nagata wrote:
> > I'm not sure this would significantly reduce the size of
> > PgStat_StatTabEntry. Could you elaborate on the expected benefits?
>
> The point is that this reduces the shmem footprint for indexes (well,
> it's also benefitial for tables, just less), on top of being cleaner
> because the stats views would only need to store and query the fields
> they care about for each relkind.

Thank you for the clarification. I think I understand your point now.

So, you mean introducing a separate stats kind for indexes, such as
PGSTAT_KIND_INDEX?

Regards,
Yugo Nagata

> --
> Michael

--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-03-26 02:52:45 Re: VACUUM FULL, CLUSTER, and REPACK block on other sessions' temp tables
Previous Message Michael Paquier 2026-03-26 02:22:25 Re: Fixes inconsistent behavior in vacuum when it processes multiple relations