The most common missing index
PostgreSQL creates indexes automatically for primary keys and unique constraints. It does not create them for foreign keys. This catches teams over and over: queries on the FK column are slow, and worse, every parent DELETE has to scan the entire child table looking for references.
Always do this
For every ... REFERENCES parent(id), add the matching index. It's so consistent that I add the index in the same migration as the FK declaration — never separately.
How to find unindexed FKs
One catalog query reveals every foreign key in the database that lacks an index on the referencing column. Run it on every database you operate.