Re: Track skipped tables during autovacuum and autoanalyze
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Yugo Nagata <nagata@sraoss.co.jp>
Cc: Sami Imseih <samimseih@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2026-03-26T23:07:29Z
Lists: pgsql-hackers
On Thu, Mar 26, 2026 at 07:22:03PM +0900, Yugo Nagata wrote: > To handle the possibility that the table is dropped between > RangeVarGetRelid() and the lock attempt, SearchSysCacheExists1() is > used after acquiring the lock. (Noticed while skimming through my emails this morning..) +void +pgstat_report_skipped_vacuum_analyze(Oid relid, bool vacuum, bool analyze, + bool autovacuum) I'd recommend to replace this interface with three booleans with a set of three bitwise flags. That would be less error prone for the callers of this function, or we could finish by aggregating counters we don't want to. -- Michael