On Sat, Feb 4, 2012 at 8:27 AM, Gary Chambers <gwch...@gwcmail.com> wrote: > 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.
That means that you didn't have the lock you were trying to release. Whether that indicates a critical error or not depends on application logic. ChrisA -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
