Reading an EXPLAIN Plan Without Fear

Turning Postgres query plans into actionable fixes.

Amit Kumar SinghJun 5, 20261 min read

The Problem

Turning Postgres query plans into actionable fixes.

This is a sample post seeded to demonstrate the curated section. Replace or delete it freely — anything you drop in this folder shows up automatically.

Why It Matters

A short note on why "Reading an EXPLAIN Plan Without Fear" is worth your attention in production systems.

Summary

Swap this file for real content when you're ready to publish.

// written by

Amit Kumar Singh

Software engineer writing about backend systems, cloud, and the realities of running code in production.

github linkedin

$ subscribe --weekly

The weekly engineering digest

Production-grade engineering writing in your inbox. No spam, unsubscribe anytime.

## related

[Backend]▲ trending

Designing Idempotent APIs That Survive Retries

Networks fail, clients retry, and duplicate requests happen. Here's how to design write endpoints that produce the same result no matter how many times they're called.

Amit Kumar SinghJun 9, 20263 min read

[Databases]▲ trending

Postgres Connection Pooling, Explained Properly

Why your serverless app exhausts Postgres connections, what a pooler actually does, and how to pick between transaction and session pooling.

Amit Kumar SinghJun 6, 20263 min read

[DevOps]▲ trending

Zero-Downtime Deployments Without the Magic

Rolling updates, health checks, and backward-compatible migrations — the unglamorous mechanics of shipping without taking the site down.

Amit Kumar SinghJun 3, 20262 min read