Re: Deadlock in PostgreSQL 7.3.4

Philipp Reisner <philipp.reisner@linbit.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