postgres deadlock without explicit locking

Question

I use PostgreSQL 9.2, and I do not use explicit locking anywhere, neither LOCK statement nor SELECT ... FOR UPDATE. However, recently I got E

Answer 1

I would suspect hash indexes first.

• Switch any hash-indexes you have to B-tree
• Use Serializable isolation level if it seems appropriate.