Re: Win32 max connections bug (causing crashes) - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Win32 max connections bug (causing crashes)
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA35530@algol.sollentuna.se
Whole thread Raw
In response to Win32 max connections bug (causing crashes)  ("Joshua D. Drake" <jd@commandprompt.com>)
List 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?

A followup question - does this happen both when the server is started
as a service and when it's started manually? Any difference in when it
dies?

//Magnus



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas DCP SD"
Date:
Subject: Re: [PATCHES] WIP archive_timeout patch
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Sorry about the GIN docs :(