On Wed, 2003-02-12 at 10:36, Robert Treat wrote:
> On Tue, 2003-02-11 at 21:00, Tatsuo Ishii wrote:
> > >
> > > while 200 may seem high, 32 definitely seems low. So, what IS a good
> > > compromise? for this and ALL the other settings that should probably be a
> > > bit higher. I'm guessing sort_mem or 4 or 8 meg hits the knee for most
> > > folks, and the max fsm settings tom has suggested make sense.
> >
> > 32 is not too low if the kernel file descriptors is not
> > increased. Beware that running out of the kernel file descriptors is a
> > serious problem for the entire system, not only for PostgreSQL.
> >
>
> Had this happen at a previous employer, and it definitely is bad. I
> believe we had to do a reboot to clear it up. And we saw the problem a
> couple of times since the sys admin wasn't able to deduce what had
> happened the first time we got it. IIRC the problem hit somewhere around
> 150 connections, so we ran with 128 max. I think this is a safe number
> on most servers these days (running linux as least) though out of the
> box I might be more inclined to limit it to 64. If you do hit a file
> descriptor problem, *you are hosed*.
>
That does seem like a more reasonable upper limit. I would rather see
people have to knowingly increase the limit rather than bump into system
upper limits and start scratching their heads trying to figure out what
the heck is going on.
--
Greg Copeland <greg(at)copelandconsulting(dot)net>
Copeland Computer Consulting