Skip site navigation (1) Skip section navigation (2)

Re: Query failed: ERROR: deadlock detected

From: Aldor <an(at)mediaroot(dot)de>
To: olly(at)lfix(dot)co(dot)uk
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Query failed: ERROR: deadlock detected
Date: 2005-08-29 17:34:21
Message-ID: 4313471D.7020404@mediaroot.de (view raw or flat)
Thread:
Lists: pgsql-admin
thanks for the explanation... i found the mistake in a new pl/pgsql
function i wrote before this error occured;-)

Oliver Elphick wrote:
> On Mon, 2005-08-29 at 16:50 +0100, Aldor wrote:
> 
>>PostgreSQL 8.0.3: Any idea what this is?
>>
>>---
>>Warning: pg_query(): Query failed: ERROR:  deadlock detected
>>DETAIL:  Process 8835 waits for ShareLock on transaction 193588236;
>>blocked by process 8834.
>>Process 8834 waits for ShareLock on transaction 193588228; blocked by
>>process 8835
>>---
>>
>>I have never seen such a log entry until now.
> 
> 
> You have two transactions locking each other out.
> 
>   For example:
>     trans A:  begin;
>     trans B:  begin;
>     trans A:  select * from table_a for update;    -- locks table_a
>     trans B:  select * from table_b for update;    -- locks table_b
>     trans A:  select * from table_b for update;    -- blocked by trans B's lock
>     trans B:  select * from table_a for update;    -- blocked by trans A's lock
> 
> Since the two transactions are blocking each other, the locks will never
> be released by the transactions that are holding them.  After a preset
> interval (about 1 second by default) a deadlock is detected and reported
> with this error message and one of the transactions is aborted.
> 
> See manual section 12.3.3 in the 8.0 documentation.
> 

In response to

pgsql-admin by date

Next:From: Antonio CaetanoDate: 2005-08-29 19:18:24
Subject: Unsubscribe
Previous:From: Oliver ElphickDate: 2005-08-29 17:25:57
Subject: Re: Query failed: ERROR: deadlock detected

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group