X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id BCBB5475925 for ; Wed, 12 Feb 2003 00:27:29 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 0CDDC4758FE for ; Wed, 12 Feb 2003 00:27:29 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1C5RW5u000933; Wed, 12 Feb 2003 00:27:32 -0500 (EST) To: Peter Eisentraut Cc: Merlin Moncure , PostgresSQL Hackers Mailing List , pgsql-advocacy@postgresql.org Subject: Re: [HACKERS] Changing the default configuration (was Re: In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Tue, 11 Feb 2003 22:13:37 +0100" Date: Wed, 12 Feb 2003 00:27:31 -0500 Message-ID: <932.1045027651@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/39 X-Sequence-Number: 797 Peter Eisentraut writes: > Tom Lane writes: >> We could retarget to try to stay under SHMMAX=4M, which I think is >> the next boundary that's significant in terms of real-world platforms >> (isn't that the default SHMMAX on some BSDen?). That would allow us >> 350 or so shared_buffers, which is better, but still not really a >> serious choice for production work. > What is a serious choice for production work? Well, as I commented later in that mail, I feel that 1000 buffers is a reasonable choice --- but I have to admit that I have no hard data to back up that feeling. Perhaps we should take this to the pgsql-perform list and argue about reasonable choices. A separate line of investigation is "what is the lowest common denominator nowadays?" I think we've established that SHMMAX=1M is obsolete, but what replaces it as the next LCD? 4M seems to be correct for some BSD flavors, and I can confirm that that's the current default for Mac OS X --- any other comments? regards, tom lane