---image: "Math and Computation/Databases/Postgres/assets/chap_7_waiting_game.png" publish: true description: "The Waiting Game: Why the database is slow today. An absurdist look at wait events, lock contention, and the physical reality of thousands of elephants bumping into each other." --- ![[chap_7_waiting_game.png]] # Chapter 7: The Waiting Game (Workloads & Wait Events) The elephant loves being lazy _alone_. But what happens when you introduce ten thousand web server connections, all demanding laziness at the exact same time? They bump into each other. If two connections try to read the same cheat sheet (Index), or worse, try to overwrite the exact same line in the diary (WAL), chaos ensues. Because Postgres refuses to corrupt your data, it forces people to stand in line. When your application is slow, 99% of the time it is because the database is resting—it is physically trapped, waiting for something else to finish, waiting for permission, or just standing awkwardly in a queue. Postgres very politely measures exactly how long you spend awkwardly standing in lines. These measurements are called **Wait Events** (or Workloads). ## Let's Meet the Bouncers and the Speed Bumps - **[[Lock|Locks]]**: The bouncers at the front door. These are "Heavyweight" locks. If someone asks for an `Exclusive Lock` on a table because they are dropping a column, every single other person trying to even look at that table gets thrown out of the club until the operation finishes. - **[[LWLock|LWLocks]] (Lightweight Locks)**: The bouncers inside the club. These are extremely fast, microscopic locks protecting individual pages in `shared_buffers` or internal data structures for nanoseconds to stop two elephants from dropping the same bucket of memory. If a million elephants try to grab a bucket at the exact same split-second down to the CPU level, they hit a `SpinLock`. - **[[IO|Disk IO]]**: The ultimate speed bump. The elephant is staring blankly at the wall, just waiting for the freezing hard drive platters to physically spin around and return its data. - **[[IPC]] (Inter-Process Communication)**: Elephants sending each other text messages and awkwardly waiting for a reply before they can continue their work. - **[[Client]]**: The saddest wait state. The database has found your data perfectly, packed it up in a box, and is now waiting for _you_ (the application server) to pick up the phone and accept the network packet. The database isn't slow; you are. - **[[Activity]] & [[Timeout]]**: The database isn't even trying to work. It's sleeping, waiting for an alarm clock, waiting for the replication stream to sync, or it's the Checkpointer snoozing heavily until it's time to frantically scrub pages to disk.