From: Jan Harasym <jan.harasym@massive.se>
To: pgsql-admin@postgresql.org
Subject: Re: Lock Error
Date: Mon, 16 Jan 2017 09:04:14 +0100
Message-ID: <19ae3169-5a61-45d1-94e6-a0a75e007953@massive.se> (raw)
In-Reply-To: <92300a1a-2c0d-2079-b2ae-e45a894ebc10@propaas.com>
References: <6d59d2ac-26cc-2452-ff10-2302a646cd6c@propaas.com>
<15916.1484101605@sss.pgh.pa.us>
<92300a1a-2c0d-2079-b2ae-e45a894ebc10@propaas.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
It would also be great to know the version of PG, since it could have
been a long fixed bug.
Thanks.
On 11/01/2017 05:50, ProPAAS DBA wrote:
> 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@propaas.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
>
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jan.harasym@massive.se
Subject: Re: Lock Error
In-Reply-To: <19ae3169-5a61-45d1-94e6-a0a75e007953@massive.se>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox