Re: 8.2.3: Server crashes on Windows using Eclipse/Junit - Mailing list pgsql-general

From Trevor Talbot
Subject Re: 8.2.3: Server crashes on Windows using Eclipse/Junit
Date
Msg-id 90bce5730710200953xee7b2d3id1b7dfc814a09a3@mail.gmail.com
Whole thread Raw
In response to Re: 8.2.3: Server crashes on Windows using Eclipse/Junit  (Rainer Bauer <usenet@munnin.com>)
List pgsql-general
On 10/20/07, Rainer Bauer <usenet@munnin.com> wrote:
> "Magnus Hagander" wrote:
>
> >> - Max_connections is set to 500. I did that originally because I kept
> >> seeing a message about no connection available and I thought it was
> >> because I was not allocating enough connections. My machine has 2GB of RAM.
> >
> >There's your problem. 500 is way above what the windows version can handle. IIRC the hard max is somewhere around
200 depending on some OS factors that we don't entirely know. I'd never recommend going above 100-150. With no more
than2Gb ram, not above 100. 
>
> My guess is that Windows is running out of handles. Each backend uses about
> 150 handles. 100 Backends means 15000 handles. Depending how many other
> programs are currently running the no. of startable backends will vary
> depending on the total handle limit Windows imposes.

Those are kernel object handles; the ceiling does depend on available
kernel memory, but they're cheap, and postgres is in no danger of
running into that limit.  Most of the handle limits people talk about
are on USER (window etc) objects, which come from a single shared
pool.

pgsql-general by date:

Previous
From: "Trevor Talbot"
Date:
Subject: Re: 8.2.3: Server crashes on Windows using Eclipse/Junit
Next
From: "Kynn Jones"
Date:
Subject: Re: Order-independent multi-field uniqueness constraint?