Tech
Your Postgres already knows why it's slow — you just have to ask it
Keeping our database fast at Atlas was part of my job — alongside writing code and shipping features. And a big chunk of that job was unglamorous: chasing slow queries, figuring out why the system dragged, asking the same handful of questions over and over.
Which indexes are we actually using? How many are just bloat? Are we vacuuming the tables that need it? Which table is quietly making every write more expensive?
I'd written SQL to answer all of it. The queries worked fine. But running ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to