From: Jan de Visser <jdevisser@digitalfairway.com>
To: pgsql-performance@postgresql.org
Subject: Re: Hanging queries on dual CPU windows
Date: Thu, 9 Mar 2006 16:15:47 -0500
User-Agent: KMail/1.9.1
References: <200603060938.00751.jdevisser@digitalfairway.com>
	<200603091507.04663.jdevisser@digitalfairway.com>
	<27202.1141935043@sss.pgh.pa.us>
In-Reply-To: <27202.1141935043@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200603091615.47323.jdevisser@digitalfairway.com>

On Thursday 09 March 2006 15:10, Tom Lane wrote:
> Jan de Visser <jdevisser@digitalfairway.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 happe=
n.
> > ...
> > 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=
,=20
myself. Can do some research though...

>
> 			regards, tom lane

jan

=2D-=20
=2D-------------------------------------------------------------
Jan de Visser =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 jdevisser@digitalfairway.com

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Baruk Khazad! Khaza=
d ai-menu!
=2D-------------------------------------------------------------