Re: Dead Lock problem with 8.1.3

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Dead Lock problem with 8.1.3
Date: 2006-09-27 17:51:04
Message-ID: 20060927175104.GB16677@phlogiston.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)crankycanuck(dot)ca
This work was visionary and imaginative, and goes to show that visionary
and imaginative work need not end up well.
--Dennis Ritchie

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2006-09-27 18:17:24 How to create nightly backups in Linux
Previous Message Joe Conway 2006-09-27 17:47:15 Re: Dead Lock problem with 8.1.3