From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan de Visser <jdevisser@digitalfairway.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hanging queries on dual CPU windows
Date: Thu, 09 Mar 2006 15:10:43 -0500
Message-ID: <27202.1141935043@sss.pgh.pa.us> (raw)
In-Reply-To: <200603091507.04663.jdevisser@digitalfairway.com>
References: <200603060938.00751.jdevisser@digitalfairway.com>
<200603091507.04663.jdevisser@digitalfairway.com>
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 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jdevisser@digitalfairway.com
Subject: Re: Hanging queries on dual CPU windows
In-Reply-To: <27202.1141935043@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox