On 9.4, I've encountered a locking message I've not seen before:
process 5293 still waiting for AccessExclusiveLock on tuple (88636,15) of relation 18238 of database 16415 after
5000.045ms
What conditions produce an "AccessExclusiveLock on tuple"? Attempting to lock a tuple when another process has done an
explicitLOCK ACCESS EXCLUSIVE?
--
-- Christophe Pettus
xof@thebuild.com