Re: Win32 max connections bug (causing crashes)

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win32 max connections bug (causing crashes)
Date: 2006-08-18 08:23:20
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA35530@algol.sollentuna.se
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?

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2006-08-18 08:50:30 Sorry about the GIN docs :(
Previous Message Zeugswetter Andreas DCP SD 2006-08-18 08:20:47 Re: [PATCHES] WIP archive_timeout patch