From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Deadlocks ?
Date: Tue, 13 May 2008 21:30:48 +0200
Message-ID: <20080513193048.GA15701@easy2.in-chemnitz.de> (raw)
In-Reply-To: <8490DCB9-7D9B-47E5-B5A6-A0FD52C30C59@kevinkempterllc.com>
References: <8490DCB9-7D9B-47E5-B5A6-A0FD52C30C59@kevinkempterllc.com>
On Tue, May 13, 2008 at 01:18:24PM -0600, kevin kempter wrote:
> we seem to be getting deadlock quite a lot. We have a python process
> that does the following and we keep getting deadlocks. Is this a real
> deadlock or maybe a wait condition? Any help in debugging / resolving
> this would be much appreciated.
An easy way to avoid deadlocks is to lock tables always in the same
order.
> cursor.execute("lock player_log_uuid in share update exclusive mode")
>
>
> >Traceback (most recent call last):
> > File "StatsParser.py", line 740, in InsertData
> > cursor.execute("lock player_log_uuid in share update exclusive
> >mode")
> >ProgrammingError: deadlock detected
> >DETAIL: Process 23098 waits for ShareUpdateExclusiveLock on
> >relation 428126 of database 427376; blocked by process 23916.
> >Process 23916 waits for ShareLock on transaction 46802680; blocked
> >by process 23098.
I've never figured out how to resolve the "lock on transaction" to
something understandable...
HTH,
Tino.
--
"What we resist, persists." (Zen saying)
www.craniosacralzentrum.de
www.forteego.de
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: postgresql@tisc.de
Subject: Re: Deadlocks ?
In-Reply-To: <20080513193048.GA15701@easy2.in-chemnitz.de>
* 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