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.045 ms
What conditions produce an "AccessExclusiveLock on tuple"? Attempting to lock
a tuple when another process has done an explicit LOCK ACCESS EXCLUSIVE?
--
-- Christophe Pettus
x...@thebuild.com
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
