Re: Dead Lock problem with 8.1.3 - Mailing list pgsql-general

From Andrew Sullivan
Subject Re: Dead Lock problem with 8.1.3
Date
Msg-id 20060927175104.GB16677@phlogiston.dyndns.org
Whole thread Raw
In response to Re: Dead Lock problem with 8.1.3  (Kai Hessing <kai.hessing@hobsons.de>)
Responses Re: Dead Lock problem with 8.1.3  (Kai Hessing <kai.hessing@hobsons.de>)
List pgsql-general
On Wed, Sep 27, 2006 at 06:46:42PM +0200, Kai Hessing wrote:
>
> Deadlock means it hangs up and doesn't terminate through timeout.

No, it doesn't.  Deadlock means, for the two deadlocked queries, both
cannot possibly finish because each waits on a lock that the other
one holds.

You can cause such deadlocks in your application, too, of course, but
they're not database deadlocks.

Also. . .

> There is no output. It just takes forever.

. . .define "forever".  Is it doing any work?  Do you see i/o?  Is it
in SELECT WAITING state?

A

--
Andrew Sullivan  | ajs@crankycanuck.ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
        --Dennis Ritchie

pgsql-general by date:

Previous
From: Joe Conway
Date:
Subject: Re: Dead Lock problem with 8.1.3
Next
From: "Andrus"
Date:
Subject: How to create nightly backups in Linux