06 October 2026
63 new posts across 9 database and data engineering sources — 7 worth your time.
Alexander Ioffe: I ran the same query twice and Postgres disagreed with itself
The author investigates why two identical EXPLAIN ANALYZE runs on statistically identical data produced opposite query plans (73 vs 3,449 heap blocks) with a tiny 1.5% margin. The post uses ExoBench to measure the planner's behavior and demonstrates an index shape that eliminates this unpredictability.
Planet PostgreSQL · 06 October 2026 · Read the original →
Hollis Varden: UUIDv4 or UUIDv7 for a primary key? 5 million rows on PostgreSQL 18
This post benchmarks UUIDv4 against the newly native UUIDv7 primary keys in PostgreSQL 18 using a 5-million-row dataset. The results show that UUIDv7 inserts took 27 seconds compared to 46 seconds for UUIDv4, with the UUIDv4 index being 29% larger, while random lookups performed identically.
Planet PostgreSQL · 06 October 2026 · Read the original →
Chris van Eijk: Row-level security performance in PostgreSQL, measured
Evaluates the performance overhead of Row-Level Security (RLS) policies in PostgreSQL 17. It analyzes the specific costs associated with function volatility, the use of `(SELECT ...)` wrappers, membership subqueries, and how the leakproof rule can inadvertently disable indexes.
Planet PostgreSQL · 06 October 2026 · Read the original →
How LinkedIn extended ClickHouse from distributed tracing to metric discovery and analytics
Details how LinkedIn scaled its ClickHouse-based observability stack to consolidate over 13 billion metrics into a single index. The system successfully handles more than 150,000 queries per minute, expanding ClickHouse's role from tracing to high-throughput metric discovery.
ClickHouse · 06 October 2026 · Read the original →
Handling hot shards
Explores the challenges of sharding database tables on a `tenant_id` column in production. It discusses how Neki's router manages data topology to handle uneven write and read distributions across shards when dealing with hot tenants.
PlanetScale · 06 October 2026 · Read the original →
Designing Neki for performance
This post details the design of Neki, a routing layer positioned between PostgreSQL clients and servers to enable sharding. It addresses the performance challenge of introducing an extra network hop and discusses the trade-offs of making multiple database servers appear as a single instance.
PlanetScale · 06 October 2026 · Read the original →
How we systematically improved our reliability
Following two major incidents in a single week, Neon outlines the systematic engineering efforts implemented to improve platform reliability. The post details the specific technical and operational changes rolled out to maintain high uptime across a rapidly growing fleet and customer base.
Neon · 06 October 2026 · Read the original →
Another week of fighting the database we chose to make our lives easier.
7 stories, every Tuesday
Published here every week. Follow by RSS to get it as it lands.