| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Unresolved Win32 bug reports |
| Date: | 2006-04-20 17:25:15 |
| Message-ID: | 20060420172515.GE1984@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2006-04-20 17:35:34 | Re: pg_dump -Ft failed on Windows XP |
| Previous Message | Jim C. Nasby | 2006-04-20 17:17:07 | Re: Unresolved Win32 bug reports |