CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.

Developer experience network

Ctrl Alt Solve

Real-world experiences, production lessons, and structured discussions — knowledge that goes beyond tutorials.

Search

Explore by technology

Open an experience to follow topics you care about.

#postgres·148#NGINX·93#networking·92#debugging·92#leadership·79#career·79#nextjs·78#edge·78#auth·78#queues·75#redis·75#observability·74#sre·74#opentelemetry·74#sql·73#performance·73

Experience feed

Unread-first ranked posts for #performance

DiscoverLatestFor you
AllQuestionExperienceDiscussionComparisonCase studyLearningProblem solvingRecommendationShowcaseCareer
LearningJul 15, 2026·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.

212 views1 likes0 comments0 bookmarks
#sql#performance#postgres
PPreeti Rani
Read →
LearningJul 21, 2026·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.

411 views0 likes0 comments0 bookmarks
#sql#performance#postgres
AAnitha Kumari
Read →
LearningJul 9, 2026·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.

406 views0 likes0 comments0 bookmarks
#sql#performance#postgres
JJamal Edwards
Read →
LearningJul 31, 2026·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.

394 views0 likes0 comments0 bookmarks
#sql#performance#postgres
SSuresh Chandra
Read →
LearningJul 29, 2026·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.

392 views0 likes0 comments0 bookmarks
#sql#performance#postgres
OOmar Farouk
Read →
LearningAug 2, 2026·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.

390 views0 likes0 comments0 bookmarks
#sql#performance#postgres
SShruthi Kamath
Read →
LearningAug 10, 2026·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.

359 views0 likes0 comments0 bookmarks
#sql#performance#postgres
AAshok Reddy
Read →
LearningAug 8, 2026·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.

359 views0 likes0 comments0 bookmarks
#sql#performance#postgres
NNikhil Sharma
Read →
LearningAug 10, 2026·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.

354 views0 likes0 comments0 bookmarks
#sql#performance#postgres
TTarun Khurana
Read →
LearningAug 8, 2026·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.

352 views0 likes0 comments0 bookmarks
#sql#performance#postgres
MMeghana Rao
Read →
LearningJul 15, 2026·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.

342 views0 likes0 comments0 bookmarks
#sql#performance#postgres
GGrace Okonkwo
Read →
LearningJul 27, 2026·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.

339 views0 likes0 comments0 bookmarks
#sql#performance#postgres
DDeepika Reddy
Read →