database_wraparound_age_datfrozenxid
Datfrozenxid wraparound ageDimensions:None
Available on:
Prometheus (1)
Interface Metrics (1)
Dimensions:None
Technical Annotations (24)
Configuration Parameters (7)
autovacuum_vacuum_thresholdautovacuum_vacuum_scale_factorautovacuum_max_workersautovacuum_naptimeautovacuum_freeze_max_agerecommended: 200000000vacuum_freeze_min_agerecommended: 50000000 (default)vacuum_freeze_table_agerecommended: 0.95 * autovacuum_freeze_max_ageError Signatures (2)
WARNING: database "mydb" must be vacuumed within 39985967 transactionslog patternERROR: database is not accepting commands to avoid wraparound data loss in database "mydb"log patternCLI Commands (3)
VACUUMremediationSELECT c.oid::regclass as table_name, greatest(age(c.relfrozenxid),age(t.relfrozenxid)) as age FROM pg_class c LEFT JOIN pg_class t ON c.reltoastrelid = t.oid WHERE c.relkind IN ('r', 'm');diagnosticSELECT datname, age(datfrozenxid) FROM pg_database;diagnosticTechnical References (12)
autovacuumcomponenttransaction ID wraparoundconceptdead tuplesconceptVACUUMcomponentcheck_postgrescomponentpg_class.relfrozenxidcomponentpg_xactfile pathpg_prepared_xactscomponentpg_stat_activitycomponentpg_stat_replicationcomponentrelfrozenxidcomponentdatfrozenxidcomponentRelated Insights (5)
Inefficient autovacuum configuration causes table bloat and transaction ID wraparound riskcritical
▸
Transaction ID wraparound prevents new transactions and causes database shutdowncritical
▸
Transaction ID wraparound forces emergency autovacuum despite disabled autovacuumcritical
▸
Transaction ID wraparound prevents new transactionscritical
▸
Autovacuum disabled on static tables delays anti-wraparound vacuumwarning
▸