| From: | Kai Hessing <kai(dot)hessing(at)hobsons(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dead Lock problem with 8.1.3 |
| Date: | 2006-09-28 16:35:36 |
| Message-ID: | 4o2buoFcjqh7U1@individual.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrew Sullivan wrote:
> 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.
Thanks for the clarification. I thought a deadlock is also, when the
system runs into an endless loop.
>> 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?
No it is not in WAITING state, it is permanently working. strace is
telling me that it is constantly accessing a file:
'postgresql/8.1/main/base/1740468/pgsql_tmp/pgsql_tmp21938.0' It doesn't
cost much performance, but it is running all the time.
Please see the full update at Message-ID: <4o2bkgFclmdhU1(at)individual(dot)net>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kai Hessing | 2006-09-28 16:39:35 | Re: Dead Lock problem with 8.1.3 |
| Previous Message | Kai Hessing | 2006-09-28 16:30:09 | Re: Dead Lock problem with 8.1.3 |