The Payment That Charged Twice
A retry is not a duplicate request — until it is. How idempotency keys actually work, why the naive version still double-charges, and the exact Postgres constraint that makes the guarantee real.
5 articles
A retry is not a duplicate request — until it is. How idempotency keys actually work, why the naive version still double-charges, and the exact Postgres constraint that makes the guarantee real.
Async I/O and a built-in uuidv7() were the headline features. One of them quietly fixed a problem I had been working around for two years; the other did less than the benchmarks promised.
You added the index, ran the query, and it is still slow. The planner is not ignoring you — it is telling you something about your data, your column order, or your types. Here is how to read what it says.
When a RAG system answers wrong, the model is usually not the culprit — the right chunk never made it into the context. Here is how to prove that, and what to fix once you have.
Tenant isolation held together by developer discipline will eventually fail, because it only takes one query. Here is how to push the boundary down into Postgres so forgetting stops being possible.