Newsdesk
Engineering
Data & AI
Industries
Enterprise Systems
Go-to-Market
Longform
DesignIndiaAll stories

Databases & Data

11 August 2026

52 new posts across 9 database and data engineering sources — 4 worth your time.

One week of Databases & Data, 4 stories, as published.

Storage Internals

The dangers of Postgres subtransactions

Explains how accumulating numerous subtransaction IDs in a single transaction degrades throughput across a PostgreSQL cluster. It highlights how this can prevent new read replicas from accepting queries during WAL replay, rendering them useless during load spikes.

Why it matters — Subtransactions can silently break read replica scaling during traffic spikes by blocking query execution during WAL replay.

PlanetScale · 11 August 2026 · Read the original →

Performance

Umair Shahid: Choosing the Right PostgreSQL Partition Key

Discusses why partitioning a large table sometimes fails to improve query performance. It explains how choosing the wrong partition key keeps queries slow and how to select the correct key to achieve the expected performance gains.

Why it matters — Partitioning is not a magic performance switch; if the partition key does not align with your query patterns, you incur the overhead of partitioning without any of the speed benefits.

Planet PostgreSQL · 11 August 2026 · Read the original →

Analytics & OLAP

How Musinsa scaled its audience engine with ClickHouse Cloud and reduced TCO by 71.4%

Details Musinsa's migration of its audience engine from self-hosted ClickHouse to ClickHouse Cloud. The transition reduced storage costs by 86.5% and total cost of ownership by up to 71.4% while simplifying ingestion.

Why it matters — Offloading infrastructure management to a managed cloud service can yield massive TCO reductions (up to 71.4%) and storage savings (86.5%) for high-scale analytical workloads.

ClickHouse · 11 August 2026 · Read the original →

Reliability

Christophe Pettus: All Your GUCs in a Row: idle_in_transaction_session_timeout

Explains the severe operational risks of idle transactions, which hold locks and block vacuum processes. It details how a single forgotten connection can trigger a cascading outage and how to use this timeout parameter to prevent it.

Why it matters — Unclosed transactions block PostgreSQL's VACUUM process, leading to table bloat and transaction ID wraparound risks that can take down an entire cluster.

Planet PostgreSQL · 11 August 2026 · Read the original →

Another week of configuring Postgres to survive our own application code.

4 stories, every Tuesday

Published here every week. Follow by RSS to get it as it lands.

← Previous issue Next issue →