Your database
Performance
Cost
Large table with only its base/PK index
Part of the Schema & indexes check · fix arrives as a guide
What it is
A large table carries only its primary key index and nothing else.
Why it matters
Any query filtering on something other than the primary key does a sequential scan of the whole table. It is fast while the table is small and becomes the application's slowest query as it grows.
How to fix it
Look at which columns the application filters and sorts by, and index those. Composite indexes ordered to match the query predicates give more than several single-column ones.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.