autovacuum_timestamp

Autovacuum start time

Dimensions:None

Available on:

Prometheus (1)

Interface Metrics (1)

Prometheus

stat_activity_autovacuum_timestamp_seconds

Start timestamp of the vacuum process in seconds

Dimensions:None

Sources

stat_activity_autovacuum_timestamp_secondsgithub.com

Technical Annotations (16)

Configuration Parameters (4)

autovacuum_vacuum_cost_delay

Controls delay between vacuum cost limit checks to optimize performance

autovacuum_vacuum_cost_limit

Sets cost limit before autovacuum sleeps to balance performance impact

autovacuum_freeze_max_age

autovacuum_max_workers

CLI Commands (5)

SELECT schemaname, relname, n_dead_tup, n_live_tup, ROUND((n_dead_tup::float / NULLIF(n_live_tup + n_dead_tup, 0)) * 100, 2) AS dead_tuple_percent, last_autovacuum, autovacuum_count FROM pg_stat_user_tables WHERE n_dead_tup > 1000 ORDER BY n_dead_tup DESC;

diagnostic

SELECT name, setting FROM pg_settings WHERE name LIKE 'autovacuum%';diagnostic

VACUUM ANALYZE your_table_name;remediation

gcloud sql instances patch INSTANCE_NAME --maintenance-window-day=SUN --maintenance-window-hour=2Schedule maintenance during low-transaction period to minimize XID advancement while autovacuum paused

VACUUM (FREEZE, VERBOSE) tablename;Manually freeze transaction IDs after maintenance if wraparound age became critical

Technical References (7)

autovacuumcomponentpgwatchcomponentpg_stat_user_tablescomponentn_dead_tupcomponentdead tuplesconcepttable bloatconcepttransaction ID wraparoundconcept

Related Insights (4)

Autovacuum falling behind on tables causes bloat accumulationwarning

▸

Dead tuple accumulation causes table bloat and performance degradationwarning

▸

High autovacuum duration causes table bloat and performance degradationwarning

▸

Cloud SQL autovacuum disabled during maintenance allows transaction ID wraparoundcritical

Cloud SQL maintenance windows can disable or suspend autovacuum for extended periods (1-4 hours) to perform updates. On high-transaction databases, this suspension allows transaction ID age to advance toward the 2-billion wraparound limit. PostgreSQL's autovacuum_freeze_max_age cannot prevent wraparound if Cloud SQL has paused autovacuum externally.

▸