Re: AccessExclusiveLock on tuple? - Mailing list pgsql-general

From Christophe Pettus
Subject Re: AccessExclusiveLock on tuple?
Date
Msg-id AC6548CD-E2C7-48EA-A3FE-B167EB94FC71@thebuild.com
Whole thread Raw
In response to Re: AccessExclusiveLock on tuple?  (Bill Moran <wmoran@potentialtech.com>)
Responses Re: AccessExclusiveLock on tuple?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Dec 2, 2015, at 9:50 AM, Bill Moran <wmoran@potentialtech.com> wrote:

> Then wait for a little while and the message will be logged.

Well, yes and no :) :

2015-12-02 10:07:40.281 PST,"xof","xof",8465,"[local]",565f3365.2111,4,"UPDATE waiting",2015-12-02 10:07:33
PST,3/12,1000056,LOG,00000,"process8465 still waiting for ShareLock on transaction 1000055 after 1001.203 ms","Process
holdingthe lock: 8428. Wait queue: 8465.",,,,"while updating tuple (0,1) in relation ""x""","update x set
a='a';",,,"psql"

Note that it's waiting for a ShareLock, not an AccessExclusiveLock, thus my question.

Just to clarify, my very specific question is about "AccessExclusiveLock".
--
-- Christophe Pettus
   xof@thebuild.com



pgsql-general by date:

Previous
From: Leonardo M. Ramé
Date:
Subject: Re: Could not connect to server: No buffer space available (0x00002747/10055)
Next
From: Tom Lane
Date:
Subject: Re: AccessExclusiveLock on tuple?