Database
Alexander Ioffe: I ran the same query twice and Postgres disagreed with itself
Planet PostgreSQL0 views
Two EXPLAIN ANALYZE runs on statistically identical data produced opposite plans, 73 heap blocks against 3,449. The margin was 1.5%. Here's the mechanism, measured with ExoBench, and the index shape that takes the coin out of the planner's hand.
Source:https://postgr.es/p/9x1PreviousChristophe Pettus: All Your GUCs in a Row: notify_buffersNextPrateek Arora: I timed 179 index recommendations on real data. 18% made the query slower.
Related posts

We're Looking for 10 dbt Developers to Test Relationship-Aware JOINs — 12 Months Free
0dev.to Data
The Best Disaster Recovery Solutions for Cross-Geography Replication (2026): Compared by What They Replicate
0dev.to Database

SQL Challenge: Can You Find the Second Purchase of Every Customer Using ROW_NUMBER()?
0dev.to Database

Database Migrations at Scale: How to Change Production Databases Without Breaking Applications
0dev.to Database

The Double-Booked Seat: Fixing a Booking Race Condition in Postgres
0dev.to Database

Preventing Duplicate Contact Names From Silently Corrupting Your Lending Ledger
0dev.to Database