Re: don't own lock of type?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: don't own lock of type?
Date: 2013-08-05 19:37:09
Message-ID: 51FFFEE5.4030209@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 08/05/2013 11:38 AM, Robert Haas wrote:
>
> On Mon, Aug 5, 2013 at 2:32 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> Hello,
>>
>> What exactly causes this?
>>
>> WARNING: you don't own a lock of type ExclusiveLock
>>
>> Does this mean the user calling the lock doesn't own the object?
>
> It means there's a bug. Either in PostgreSQL, or some loadable module
> you're using.

I am getting this rather frequently, I will check modules but I don't
believe we are running any.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-08-05 19:38:34 Re: Disabling ALTER SYSTEM SET WAS: Re: ALTER SYSTEM SET command to change postgresql.conf parameters
Previous Message Atri Sharma 2013-08-05 19:36:20 Moving 'hot' pages from buffer pool to heap