MTAR T3D Sessions: Why XIDs Are Still a Problem in Postgres

Welcome back to More Than a Refresh Presents: T3D Sessions. In this Postgres Pet Peeves episode, Justin Graf and JD take on a long-standing issue in PostgreSQL: transaction IDs (XIDs) and what happens when they wrap around. Despite years of improvements, the system still relies on a 32-bit design that forces ongoing maintenance in high-volume databases. For teams running large or active systems, this means dealing with constant background processes like freezing and cleanup. While these processes have improved over time, they don’t remove the underlying constraint, they work around it. Justin explains why this isn’t a new problem, but one rooted in design decisions made decades ago. And while there have been attempts to move beyond it, most real-world solutions today focus on managing the impact rather than eliminating the cause. This short session offers a practical look at why XIDs still matter and how they continue to shape performance and operations in modern Postgres environments. 🎧 Listen to all More Than a Refresh episodes: https://www.commandprompt.com/mtar/ 💼 Learn more about Command Prompt: https://www.commandprompt.com 🔧 PostgreSQL Services: https://www.commandprompt.com/services/ 🖥 PgManage – Open Source GUI for PostgreSQL, MariaDB & more: https://www.commandprompt.com/product... 🛡 PgLTS – Long-term support for EOL PostgreSQL: https://www.commandprompt.com/product... 📲 Connect with us: LinkedIn: https://www.commandprompt.com/linkedin Facebook: https://www.commandprompt.com/facebook Twitter/X: https://www.commandprompt.com/twitter BlueSky: https://www.commandprompt.com/bluesky 📬 Contact us: https://www.commandprompt.com/contact...