I've been experimenting with concurrent VACUUMs and getting occasional
instances of
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
ERROR: WaitOnLock: error on wakeup - Aborting this transaction
It would be really nice if I could find out the particular locks that
are causing this conflict --- but the code that emits these messages
isn't very transparent :-(. Can anyone explain how to determine just
what the deadlock is?
regards, tom lane