Hi, > -----Original Message----- > From: pgsql-performance-owner@xxxxxxxxxxxxxx > [mailto:pgsql-performance-owner@xxxxxxxxxxxxxx] On Behalf Of Tom Lane > Sent: Thursday, March 09, 2006 9:11 PM > To: Jan de Visser > Cc: pgsql-performance@xxxxxxxxxxxxxx > Subject: Re: [PERFORM] Hanging queries on dual CPU windows > > > Jan de Visser <jdevisser@xxxxxxxxxxxxxxxxxx> 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 ... Debugging Tools for Windows from Microsoft http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx Additinonally you need a symbol-file or you use "SRV*c:\debug\symbols*http://msdl.microsoft.com/download/symbols"; to load the symbol-file dynamically from the net. Best regards > > regards, tom lane > > ---------------------------(end of > broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings Hakan Kocaman Software-Development digame.de GmbH Richard-Byrd-Str. 4-8 50829 Köln Tel.: +49 (0) 221 59 68 88 31 Fax: +49 (0) 221 59 68 88 98 Email: hakan.kocaman@xxxxxxxxx
