Ctrl Alt Solve

Learning14d ago·1 entry

I finally understood Postgres indexes the hard way

I used to think more indexes always meant faster queries. Production taught me about write amplification and table bloat instead. We had three indexes that nothing queried, slowing every insert. EXPLAIN ANALYZE finally showed which plans actually used which indexes. After dropping the dead ones, writes got healthier without hurting reads. Now I review unused indexes in the same ritual as reviewing slow queries.

206 views0 likes0 comments0 bookmarks

#sql #performance #postgres

RRohan Verma Read →

Problem solving15d ago·1 entry

a silent 502 that only hit 2% of traffic

No spike in CPU. Error budgets looked fine at a glance. Users still reported blank pages in a thin slice of traffic. Logs only showed upstream resets with no clear application exception. The culprit was a stale keep-alive timeout between nginx and the app. Aligning idle timeouts stopped the intermittent 502s within an hour. We also added a dashboard for upstream reset reasons so the next page is faster.

323 views0 likes0 comments0 bookmarks

#NGINX #debugging #networking

Rohan Verma

Rohan Verma

Experiences shared

I finally understood Postgres indexes the hard way

a silent 502 that only hit 2% of traffic