| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | pgsql-general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: AccessExclusiveLock on tuple? |
| Date: | 2015-12-02 18:18:28 |
| Message-ID: | AC6548CD-E2C7-48EA-A3FE-B167EB94FC71@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Dec 2, 2015, at 9:50 AM, Bill Moran <wmoran(at)potentialtech(dot)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,"process 8465 still waiting for ShareLock on transaction 1000055 after 1001.203 ms","Process holding the 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(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-02 18:29:16 | Re: AccessExclusiveLock on tuple? |
| Previous Message | Leonardo M. Ramé | 2015-12-02 18:07:10 | Re: Could not connect to server: No buffer space available (0x00002747/10055) |