Win32 max connections bug (causing crashes)

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Win32 max connections bug (causing crashes)
Date: 2006-08-09 23:17:10
Message-ID: 44DA6CF6.8020201@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

I had a customer call in today they are running Win2003 with 22 gig of
ram (that may be a mistype on their end, it may be 32gigs of ram).

They cranked up their postgresql max_connections to 500.

When PostgreSQL hits above 400, it dies and I don't mean a slow crawl
type death. A death where all connections close and the database does a
rollback and restart.

I was able to reproduce with a simple pgbench on my own win32 environment.

I wasn't able to go above 300 with mine.

Any thoughts?

Joshua D. Drake

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2006-08-09 23:25:50 Re: new job
Previous Message Tom Lane 2006-08-09 23:05:46 Re: Plugins redux (was Re: [PATCHES] PL instrumentation