hard20 pts · first answer countspostgresqlmvcc

Transaction ID wraparound

Monitoring shows age(datfrozenxid) for a PostgreSQL database is close to 2 billion and climbing. What happens if nothing is done?

A.PostgreSQL will eventually refuse new write transactions to protect data until the database is vacuumed and old XIDs are frozenB.PostgreSQL will silently delete the oldest rows to free IDsC.Nothing; transaction IDs are 64-bit on disk and can never run outD.Replicas will automatically become the new primary

← Fixing a recurring deadlock Partition pruning →