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
Every deploy gave a full share of traffic to JVMs that had not compiled anything yet
0dev.to
My Journey so Far as a Freshman Software Engineering Student at YIBS (ISEST)
0dev.to Beginners
Building Secure Authentication: Important Practices for Backend Developers
0dev.to Node
The Specification Pattern in Spring Data JPA: Building Composable Queries That Scale
0dev.to Java
How We Parsed SQLite 3 B-Tree Pages, Overflow Chains, and DuckDB SUMMARIZE in Pure TypeScript
0dev.to Database
Why Random UUID v4 Primary Keys Hurt Postgres Write Latency (And How RFC 9562 UUID v7 Fixes It)
0dev.to Database