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

Re: Deadlock in PostgreSQL 7.3.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Philipp Reisner <philipp(dot)reisner(at)linbit(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Deadlock in PostgreSQL 7.3.4
Date: 2003-08-18 13:38:00
Message-ID: 22060.1061213880@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Philipp Reisner <philipp(dot)reisner(at)linbit(dot)com> writes:
> Now if the applications issues one delete statement concurrently on 
> two connections both block forever. 

> Please correct me if I am wrong, but should not one of the statements
> succeed and the other simply fail ?

> Aug 18 10:34:25 nut1 postgres[4934]: [44389] LOG:  
>                      query: delete from Calls where objID = 2268645

> Aug 18 10:34:25 nut1 postgres[4933]: [44071] LOG:  
>                      query: delete from Calls where objID = 2268645

>  4933 ?        S      5:20 postgres: sd sd 10.2.1.5 idle in transaction
>  4934 ?        S      5:08 postgres: sd sd 10.2.1.5 DELETE waiting

I see no deadlock.  4933 is waiting for its client to issue another
command.  4934 is waiting to see if it can delete the row.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Marcus EnglandDate: 2003-08-18 14:31:58
Subject: Re: Database Grants Bug
Previous:From: Philipp ReisnerDate: 2003-08-18 11:04:58
Subject: Deadlock in PostgreSQL 7.3.4

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