Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cT7ta-0005MQ-LE for pgsql-admin@arkaria.postgresql.org; Mon, 16 Jan 2017 14:04:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cT7tY-0007da-TW for pgsql-admin@arkaria.postgresql.org; Mon, 16 Jan 2017 14:04:24 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cT2Ij-0002CQ-MX for pgsql-admin@postgresql.org; Mon, 16 Jan 2017 08:06:01 +0000 Received: from pdc-mail-out01.ubisoft.com ([195.22.144.43]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cT2Ic-0006ZK-CC for pgsql-admin@postgresql.org; Mon, 16 Jan 2017 08:06:00 +0000 Subject: Re: Lock Error DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=massive.se; s=p160727; t=1484553949; bh=bbOVXSPDNmFBc7j93YVOal3IIlUbsoHnO+JnS0cswro=; h=To:References:From:Date:In-Reply-To; b=Grmy5VaPyIMOhgCZcDbpD/kBD+yl+VEAQWda6KiGGTOjwcmJqd5C2Xrpl4TDAL2rd fLMyO0O2oPPfdeXN3UnvESzmX9C3IJv8LrPB373m7WRiKcpMIPuk4HIOOlBRaz0Ara 3+3bzTgrNsLjDIgaCffKGzlLHTooe9Fa27w9ERP8mSGFAbKrHKwI+9kb488AhIrGmB 02y5uZchzKn7wrn/jUXUe91laZuxTMuwAHFhlpgF17diMQTEU8MZoJAqSqhJYC5HSO 5H+3lcIMWbHH8LBAtM3Uk494T0nx+j37U7C+R5m2nYzYyMhsjF67Nvys1IpjOrOlBO MmKIqO51TdusQ== To: References: <6d59d2ac-26cc-2452-ff10-2302a646cd6c@propaas.com> <15916.1484101605@sss.pgh.pa.us> <92300a1a-2c0d-2079-b2ae-e45a894ebc10@propaas.com> X-Ubisoft-Relay: yes From: Jan Harasym Message-ID: <19ae3169-5a61-45d1-94e6-a0a75e007953@massive.se> Date: Mon, 16 Jan 2017 09:04:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <92300a1a-2c0d-2079-b2ae-e45a894ebc10@propaas.com> Content-Type: multipart/alternative; boundary="------------AE230CEE028293C58D515854" X-Originating-IP: [10.35.3.63] X-ClientProxiedBy: PDC-MAIL-EXCH01.ubisoft.org (10.0.2.27) To PDC-MAIL-EXCH05.ubisoft.org (10.0.2.31) X-Pg-Spam-Score: -4.3 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --------------AE230CEE028293C58D515854 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit 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 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 > > > --------------AE230CEE028293C58D515854 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: 8bit

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




--------------AE230CEE028293C58D515854--