
PostgreSQL’s powerful query planner relies heavily on up-to-date table and column statistics to decide whether to use indexes or full-table scans for your queries. When these statistics become outdated—often after bulk updates or large data changes—Postgres can start making bad decisions, causing indexes to be ignored and query performance to drop sharply.