Re: don't own lock of type?

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

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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2013-08-05 18:44:28 Re: Unsafe GUCs and ALTER SYSTEM WAS: Re: ALTER SYSTEM SET
Previous Message Robert Haas 2013-08-05 18:37:34 Re: HeapTupleSatisfiesDirty fails to test HEAP_XMAX_IS_LOCKED_ONLY for TransactionIdIsInProgress(...)