JPJagdish Pariharinblog.jatin510.dev·5h ago · 18 min readMVCC Explained: Build Postgres-Style Snapshots in 100 Lines of TypeScript Part of the Nothing is magic series, where we build database internals from scratch until they stop being magic. Open two psql sessions. Session A: BEGIN; DELETE FROM users; -- deletes all 1 million30
Iilshaadincodeless-sync.hashnode.dev·5h ago · 11 min readHow Often Should You Sync Billing Data to Postgres?You have your billing data landing in Postgres. The connection works, the table is there, the first sync completed. Now there is a dropdown asking how often you want to repeat it, and no obvious way t00
KMKrishnam Murarkainedilec-engineering.hashnode.dev·5h ago · 3 min readAn Outbox Makes the Write Atomic. It Does Not Make Delivery Exactly-Once.The transactional outbox exists to close one gap. A service has to change its own database and tell other services about it, and a database transaction cannot commit to a broker. Write state first and10
UUanikinuanik.hashnode.dev·20h ago · 4 min readHaversine vs PostGIS: A Small Experiment with 1 Million LocationsI was working on a location-based search for a service marketplace.The requirement was simple: Given a user's latitude and longitude, find nearby service providers and order them by distance. My fir00
Jjaberadam2001insimplyexplained.hashnode.dev·1d ago · 8 min readWhy Your Database Is Ignoring the Index You Just AddedEveryone tells you the same thing when a query gets slow: "add an index." So you did. And it's still slow. The index is sitting right there — and your database is flat-out ignoring it. Here are the fi20
KSkiran sabneinkiransabne.dev·2d ago · 17 min readHow to Read a PostgreSQL Execution Plan: The Complete Guide (With Real Examples)If you've ever run EXPLAIN ANALYZE on a slow PostgreSQL query and stared at a wall of text with no idea what to do next, this guide is for you. We'll go from "what is this tree" to "here's exactly how20
Jjaberadam2001insimplyexplained.hashnode.dev·2d ago · 9 min readThe N+1 Query Problem: Why Your App Is Fast in Dev and Slow in ProductionThe page loaded in 15 milliseconds on your laptop. In production it takes 8 seconds — and the slow-query log is empty. This is the N+1 query problem: the most common performance bug you'll ever ship, 00
AAA Adarshinadarshgowda.hashnode.dev·4d ago · 7 min readOne database is a cost, not a simplificationMost features arrive needing one kind of storage. Occasionally one arrives needing two, and that's where a specific bad decision gets made — almost always for a good reason. The shape is recognisable.00
UAUptime Architectinuptimearchitect.hashnode.dev·4d ago · 14 min readOracle SQL Plan Management: Stop a Good Plan From Going BadA query that ran in fifty milliseconds for a year is suddenly taking thirty seconds. Nobody changed the code. Nobody changed the query. And that's exactly the problem: the optimizer is allowed to chan10
Uuntactitinuntactit.hashnode.dev·5d ago · 4 min read24 of the 30 duplicate groups were not duplicatesWe grouped an asset database by title and found 30 groups of "duplicates." Content hashing dissolved 24 of them. Five were real. One was unjudgeable — because the rows had no content at all. This is a00
