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.

Search

Find people and experiences by name, username, role/title, keyword, or technology tag.

Popular tags

#postgres#queues#redis#observability#sre#opentelemetry#networking#career#nginx#leadership#debugging#nextjs#edge#auth#billing#migration#architecture#typescript#api#dx#webhooks#testing#ci#slack
40 posts tagged #sql
Learning15d 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.

307 views0 likes0 comments0 bookmarks
#postgres#sql#performance
MMadhavi Latha
Read →
Learning15d 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.

306 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Bhavya Arora
Learning27d 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.

403 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Manasa Priya
LearningAug 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.

410 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Helena Costa
Learning19d 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.

343 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Ajay Varma
LearningSep 6, 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.

383 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Nithin Reddy
LearningSep 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.

377 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Jordan Blake
Learning21d 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.

338 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Priya Nair
Learning19d 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.

321 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Anitha Selvam
Learning15d 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.

263 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Tejaswini
Learning21d 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.

330 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Arun Kumar
LearningAug 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.

336 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Chloe Nguyen
LearningSep 6, 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.

298 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Kenji Sato
LearningAug 23, 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.

299 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Amitabh Tiwari
LearningAug 23, 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.

269 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Ananya Gupta
LearningAug 19, 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.

261 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Vivek Saxena
LearningSep 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.

256 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Latha Menon
LearningAug 23, 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.

254 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Suresh Babu
LearningAug 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.

249 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Patrick O'Neill
LearningAug 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.

239 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Pooja Sri
Learning15d 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.

153 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Deepak Bisht
LearningSep 6, 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.

205 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Revathi
Learning27d 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.

163 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Owen Hart
LearningAug 25, 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.

166 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Mei Ling Zhou
LearningSep 6, 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.

156 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Sofia Alvarez
LearningAug 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.

153 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Priya Lakshmi
Learning17d 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.

116 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Meera Kapoor
LearningAug 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.

139 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Shruthi Kamath
LearningAug 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.

120 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Amelia Scott
Learning27d 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.

109 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Anitha Kumari
Learning17d 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.

88 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Rebecca Stone
LearningAug 19, 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.

103 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Shreya Khanna
LearningAug 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.

99 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Pranav Chopra
Learning21d 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.

80 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Marcus Webb
LearningAug 19, 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.

81 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Balaji Sundaram
Learning29d 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.

79 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Ajith Kumar
LearningSep 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.

65 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Sowmya Nair
LearningAug 19, 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.

62 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Anjali Mehra
LearningAug 25, 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.

61 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Uday Kiran
LearningAug 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.

55 views0 likes0 comments0 bookmarks
#postgres#sql#performance
Maya Chen
B
Read →
M
Read →
H
Read →
A
Read →
N
Read →
J
Read →
P
Read →
A
Read →
T
Read →
A
Read →
C
Read →
K
Read →
A
Read →
A
Read →
V
Read →
L
Read →
S
Read →
P
Read →
P
Read →
D
Read →
R
Read →
O
Read →
M
Read →
S
Read →
P
Read →
M
Read →
S
Read →
A
Read →
A
Read →
R
Read →
S
Read →
P
Read →
M
Read →
B
Read →
A
Read →
S
Read →
A
Read →
U
Read →
M
Read →