As one of the PostgreSQL kernel resources, the transaction ID (XID) will be gradually consumed (wrap-up) during the execution of the transaction. The kernel continuously recovers the consumed stock transaction IDs in the background through Vacuum to avoid exhaustion. When a single table is too large, the data space of a single instance is too large, or the instance is under high-frequency insert, delete, and update operations for a long time, the speed of Vacuum recovering transaction IDs will be lower than the rate at which the instance consumes transaction IDs through insert, delete, and update. This will lead to transaction ID exhaustion and cause the instance to be unable to write. To avoid this situation, the recommendations are:

When a single table is larger than 1TB or the TPS of the entire instance is frequently greater than 1,000, you can design sharding according to the business situation.

Pay attention to the "Database maximum age XIDs" monitor item daily and configure related alarm policies. If an alarm is received, you can submit a ticket or contact Volcano technical support for assistance in troubleshooting and resolution.

Last updated: 2025.11.17 16:15:12

Public security network record in Beijing: No. 11010802032137