Re: Warning: you don't own a lock of type ExclusiveLock - Mailing list pgsql-general

From Chris Angelico
Subject Re: Warning: you don't own a lock of type ExclusiveLock
Date
Msg-id CAPTjJmo9Sb45C6G2PDHT7mNXD-M8C0ScMqekgsn7SzX4hovD3w@mail.gmail.com
Whole thread Raw
In response to Warning: you don't own a lock of type ExclusiveLock  (Gary Chambers <gwchamb@gwcmail.com>)
Responses Re: Warning: you don't own a lock of type ExclusiveLock  (Gary Chambers <gwchamb@gwcmail.com>)
List pgsql-general
On Sat, Feb 4, 2012 at 8:27 AM, Gary Chambers <gwchamb@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

pgsql-general by date:

Previous
From: Gary Chambers
Date:
Subject: Warning: you don't own a lock of type ExclusiveLock
Next
From: Tom Lane
Date:
Subject: Re: Puzzling full database lock