Re: Lock Error

From: ProPAAS DBA <dba(at)propaas(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Lock Error
Date: 2017-01-11 04:50:13
Message-ID: 92300a1a-2c0d-2079-b2ae-e45a894ebc10@propaas.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I'll check with the client and see if we can re-create it, they claim
this error is happening daily. Would a log file help to start with?

On 01/10/2017 07:26 PM, Tom Lane wrote:
> ProPAAS DBA <dba(at)propaas(dot)com> writes:
>> Anyone know what the cause of this error might be?
>> ERROR: lock main [some number] is not held
> That would be a bug. If you can reproduce it, we'd like to see how.
>
> regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message gleeco 2017-01-11 19:30:39 Re: vacuum toast loop?
Previous Message Tom Lane 2017-01-11 02:26:45 Re: Lock Error