From: | Jan de Visser <jdevisser(at)digitalfairway(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Hanging queries on dual CPU windows |
Date: | 2006-03-09 21:15:47 |
Message-ID: | 200603091615.47323.jdevisser@digitalfairway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thursday 09 March 2006 15:10, Tom Lane wrote:
> 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?
CPU drops off. In fact, that's my main clue something's wrong ;-)
>
> 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 ...
I wouldn't know. I'm hardly a windows expert. Prefer not to touch the stuff,
myself. Can do some research though...
>
> regards, tom lane
jan
--
--------------------------------------------------------------
Jan de Visser jdevisser(at)digitalfairway(dot)com
Baruk Khazad! Khazad ai-menu!
--------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2006-03-09 21:22:04 | Re: Hanging queries on dual CPU windows |
Previous Message | Tom Lane | 2006-03-09 20:10:43 | Re: Hanging queries on dual CPU windows |