# 4.6 The Infinite Calendar (Case Study)
Postgres is designed to live forever. But even an elephant's memory has a physical limit. In this case study, we explore the database equivalent of the "Millennium Bug": **Transaction ID Wraparound**.
## The Box of Name Tags
Every time an elephant starts a new transaction, he is given a **Name Tag (Transaction ID)**. These tags are represented by a `uint32` number. As we've seen, these tags are crucial for **[[Chapter 1/1.4 - MVCC|MVCC]]**—they determine whether a suitcase is "visible" to you.
But a 32-bit number only goes up to roughly **4 billion**.
Imagine a cafe that has been open for a hundred years. Eventually, the elephant reaches Name Tag #4,294,967,295. He reaches into the box for the next tag, and... there are no more!
## The Re-run (The Crisis of Identity)
If the elephant simply went back to #1, chaos would erupt. The elephant would look at a suitcase created seventy years ago (labeled #1) and think it was created *this afternoon*!
To prevent this identity crisis, the database uses a **Circular Timeline**. It treats the numbers like a 360-degree circle. But for the circle to work, the elephant must never be more than **2 billion** steps ahead of the oldest "live" tag.
If a single Name Tag gets too old—if it was created more than 2 billion transactions ago—the elephant loses his mind. He can no longer tell the past from the future!
## The Frozen Secret (FREEZE)
To save us from this doom, the **[[Chapter 5/5.3 - The Housekeepers|Housekeepers]]** perform a ritual known as **FREEZE**.
When a row is very old and we know it will never be changed again, the vacuum worker stamps it with a special **"Frozen"** mark. This mark tells the elephant: *"Ignore the number on this Name Tag. This suitcase is so old it's basically part of the furniture. It is visible to everyone, forever."*
## The Diagnostics: Checking the Calendar
To avoid an identity crisis, you must keep a close eye on the **Age of the Depot**:
```sql
-- How close are we to the end of the world?
SELECT datname, age(datfrozenxid)
FROM pg_database
ORDER BY age(datfrozenxid) DESC;
```
- **Age < 100 Million**: The elephant is young and healthy.
- **Age > 1 Billion**: The elephant is getting nervous.
- **Age > 2 Billion**: **THE DEPOT IS ON FIRE.**
If the age reaches the limit, Postgres will perform a **Panic Shutdown**. It will refuse to allow any new writes and will only let you log in as a superuser to run a manual vacuum. It is a "Safe Mode" for the apocalypse.
## The Lesson of the Timeline
Transaction Wraparound is rare, but for massive, high-velocity databases, it is the ultimate "End Boss." By ensuring your housekeepers are healthy and your columns are regularly frozen, you ensure the Elephant Cafe can keep its doors open for a thousand years.
---
[[Chapter 4/4.5 - The Looking Glass Windows|← 4.5 - The Looking Glass Windows]] | [[Chapter 4/4.0 - Safety Without Sweating|↑ 4.0 - Safety Without Sweating]] | [[Chapter 5/5.0 - The Hunger of Resources|5.0 - The Hunger of Resources →]]