Search Postgresql Archives

Warning: you don't own a lock of type ExclusiveLock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



All,

I have a recently-migrated Pg cluster running 8.4.7 on Red Hat Enterprise
Linux Client release 5.7 (Tikanga) in a VMware VM that is logging the
subject warning.  The application code is considerably old (deployed back in
the 7.4 days, I believe) and the message is preceded by a call to select
user_write_unlock(), which is a simple wrapper query that calls
pg_advisory_unlock().  What are the causes and possible problems and
side-effects of receiving such a log warning?  Thank you for any assistance
you can provide.

--
Gary Chambers

--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux