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

From: Chris Angelico <rosuav(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Warning: you don't own a lock of type ExclusiveLock
Date: 2012-02-04 02:19:32
Message-ID: CAPTjJmo9Sb45C6G2PDHT7mNXD-M8C0ScMqekgsn7SzX4hovD3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Feb 4, 2012 at 8:27 AM, Gary Chambers <gwchamb(at)gwcmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-02-04 06:00:46 Re: Puzzling full database lock
Previous Message Rodrigo E. De León Plicet 2012-02-04 01:53:15 Re: Don't Thread On Me (PostgreSQL related)