Neues vom PostgreSQL Planet

Every database eventually runs into the same wall: storage costs money, and the data nobody queries anymore costs exactly as much as the data everyone does. A five-year-old row occupies the same expensive block storage as the order that came in thirty seconds ago. Postgres doesn't know the difference, and why would it? That's honestly a common refrain among most database engines.As a result, many have dreamed of fixing this by decoupling compute from storage.

Before starting, I want to put a few things at the top:

Diagnose index scan performance problems by temporarily disabling index scans or bitmap scans and measuring what the planner chooses instead.