Re: Changing the default configuration - Mailing list pgsql-hackers

From Robert Treat
Subject Re: Changing the default configuration
Date
Msg-id 1045067779.12931.258.camel@camel
Whole thread Raw
In response to Re: Changing the default configuration  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: Changing the default configuration
Re: Changing the default configuration
Re: Changing the default configuration
Re: Changing the default configuration
List pgsql-hackers
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*.

Robert Treat




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Q about InsertIndexResult
Next
From: Andrew Sullivan
Date:
Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy]