X-Original-To: pgsql-hackers@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 11211475A80 for ; Wed, 12 Feb 2003 11:36:28 -0500 (EST) Received: from localhost.localdomain (unknown [65.217.53.66]) by postgresql.org (Postfix) with ESMTP id 661FD475A45 for ; Wed, 12 Feb 2003 11:36:27 -0500 (EST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by localhost.localdomain (8.12.5/8.12.5) with ESMTP id h1CH1d6P007642; Wed, 12 Feb 2003 12:01:39 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id h1CGaJj29503; Wed, 12 Feb 2003 11:36:19 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id CWVL1BQL; Wed, 12 Feb 2003 11:36:19 -0500 Subject: Re: Changing the default configuration From: Robert Treat To: Tatsuo Ishii Cc: scott.marlowe@ihs.com, pgsql-hackers@postgresql.org In-Reply-To: <20030212.110000.97298009.t-ishii@sra.co.jp> References: <20030212.101008.41630074.t-ishii@sra.co.jp> <20030212.110000.97298009.t-ishii@sra.co.jp> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 12 Feb 2003 11:36:19 -0500 Message-Id: <1045067779.12931.258.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/493 X-Sequence-Number: 35435 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