X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (mx2.hub.org [200.46.204.254])
	by postgresql.org (Postfix) with ESMTP id C2CC511F7D2F
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu, 20 Apr 2006 14:25:36 -0300 (ADT)
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 required=5 tests=[AWL=0.257, BAYES_00=-2.599]
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024)
	with ESMTP id jc08trlCk3DI
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu, 20 Apr 2006 14:25:26 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from svana.org (svana.org [125.62.94.225])
	by postgresql.org (Postfix) with ESMTP id 0A55211F7C7B
	for <pgsql-hackers@postgreSQL.org>;
	Thu, 20 Apr 2006 14:25:24 -0300 (ADT)
Received: from kleptog by svana.org with local (Exim 4.50)
	id 1FWcu3-00022V-2t; Fri, 21 Apr 2006 03:25:15 +1000
Date: Thu, 20 Apr 2006 19:25:15 +0200
From: Martijn van Oosterhout <kleptog@svana.org>
To: "Jim C. Nasby" <jnasby@pervasive.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: Unresolved Win32 bug reports
Message-ID: <20060420172515.GE1984@svana.org>
Reply-To: Martijn van Oosterhout <kleptog@svana.org>
References: <200604201102.k3KB21H07902@candle.pha.pa.us>
	<20060420171707.GD49405@pervasive.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Q8BnQc91gJZX4vDc"
Content-Disposition: inline
In-Reply-To: <20060420171707.GD49405@pervasive.com>
X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6
X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522  48A7 6394 F08A 0DC6 7BE6
X-PGP-Key-URL: <http://svana.org/kleptog/0DC67BE6.pgp.asc>
User-Agent: Mutt/1.5.9i
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: kleptog@svana.org
X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false
X-Archive-Number: 200604/740
X-Sequence-Number: 82463


--Q8BnQc91gJZX4vDc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 20, 2006 at 12:17:07PM -0500, Jim C. Nasby wrote:
> Here's one to add to the list: running pgbench with a moderately heavy
> load on an SMP box likes to trigger a state where the database (or
> pgbench) just stops doing work (CPU usage drops to nothing, as does disk
> activity). I've been able to repro this on 2 Intel boxes (one a 2 way,
> one a 4 way), and a dual Opteron, all running the latest windows binary.
> A 50 connection test running 1000 transactions is pretty much ensured to
> fail.

Well, this sounds like a dead-lock, the obvious step would be to
attached gdb to both and get a stack-trace...
--=20
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to l=
itigate.

--Q8BnQc91gJZX4vDc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFER8P6IB7bNG8LQkwRAiPCAJ9F8CXMyXQxCLUdbgpJ/NtLqdzLjwCfQRNJ
1xBCAenYjbz7BbcSk1OsZG0=
=B96x
-----END PGP SIGNATURE-----

--Q8BnQc91gJZX4vDc--