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 21:00:27 -0500
Message-ID: <200603092100.27527.jdevisser@digitalfairway.com> (raw)
In-Reply-To: <27202.1141935043@sss.pgh.pa.us>
References: <200603060938.00751.jdevisser@digitalfairway.com>
<200603091507.04663.jdevisser@digitalfairway.com>
<27202.1141935043@sss.pgh.pa.us>
On Thursday 09 March 2006 15:10, Tom Lane wrote:
> 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 ...
Here ya go:
http://www.devisser-siderius.com/stack1.jpghttp://www.devisser-siderius.com/stack2.jpghttp://www.devisser-siderius.com/stack3.jpg
There are three threads in the process. I guess thread 1 (stack1.jpg) is the
most interesting.
I also noted that cranking up concurrency in my app reproduces the problem in
about 4 minutes ;-)
With thanks to Magnus Hagander for the Process Explorer hint.
jan
--
--------------------------------------------------------------
Jan de Visser jdevisser@digitalfairway.com
Baruk Khazad! Khazad ai-menu!
--------------------------------------------------------------
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: jdevisser@digitalfairway.com
Subject: Re: Hanging queries on dual CPU windows
In-Reply-To: <200603092100.27527.jdevisser@digitalfairway.com>
* 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