From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Hanging queries on dual CPU windows |
Date: | 2006-03-09 20:10:43 |
Message-ID: | 27202.1141935043@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Jan de Visser <jdevisser(at)digitalfairway(dot)com> writes:
> Furtermore, it does not happen on Linux machines, both single CPU and dual
> CPU, nor on single CPU windows machines. We can only reproduce on a dual CPU
> windows machine, and if we take one CPU out, it does not happen.
> ...
> Which showed me that several transactions where waiting for a particular row
> which was locked by another transaction. This transaction had no pending
> locks (so no deadlock), but just does not complete and hence never
> relinquishes the lock.
Is the stuck transaction still consuming CPU time, or just stopped?
Is it possible to get a stack trace from the stuck process? I dunno
if you've got anything gdb-equivalent under Windows, but that's the
first thing I'd be interested in ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jan de Visser | 2006-03-09 21:15:47 | Re: Hanging queries on dual CPU windows |
Previous Message | Jan de Visser | 2006-03-09 20:07:04 | Re: Hanging queries on dual CPU windows |