From: Alvaro Herrera <alvherre@commandprompt.com>
To: kevin kempter <kevin@kevinkempterllc.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tino Schwarze <postgresql@tisc.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: Deadlocks ?
Date: Tue, 13 May 2008 20:49:33 -0400
Message-ID: <20080514004933.GR6966@alvh.no-ip.org> (raw)
In-Reply-To: <506ECCFC-6568-4CD3-B4AF-25A860D97859@kevinkempterllc.com>
References: <8490DCB9-7D9B-47E5-B5A6-A0FD52C30C59@kevinkempterllc.com>
<20080513193048.GA15701@easy2.in-chemnitz.de>
<7586.1210719628@sss.pgh.pa.us>
<506ECCFC-6568-4CD3-B4AF-25A860D97859@kevinkempterllc.com>
kevin kempter wrote:
>>> On Tue, May 13, 2008 at 01:18:24PM -0600, kevin kempter wrote:
>>> 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.
> If that's true does it make sense to play with a timeout value (I assume
> the timeout is configurable somewhere in postgresql.conf) in an effort to
> tune for this ?
If there's a deadlock, it's gonna wait until detected, so no matter
how large you set the timeout, there's no getting out of it.
If it were a plain lock wait, it would make sense to try to increase the
timeout.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: alvherre@commandprompt.com, kevin@kevinkempterllc.com, tgl@sss.pgh.pa.us, postgresql@tisc.de
Subject: Re: Deadlocks ?
In-Reply-To: <20080514004933.GR6966@alvh.no-ip.org>
* 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