X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 2A8544758C9 for ; Wed, 12 Feb 2003 22:08:26 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A4283474E42 for ; Wed, 12 Feb 2003 22:08:24 -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 h1D38Q5u009701; Wed, 12 Feb 2003 22:08:26 -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 "Thu, 13 Feb 2003 00:52:25 +0100" Date: Wed, 12 Feb 2003 22:08:26 -0500 Message-ID: <9700.1045105706@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/53 X-Sequence-Number: 811 Peter Eisentraut writes: > I know you like it in that range, and 4 or 8 MB of buffers by default > should not be a problem. But personally I think if the optimal buffer > size does not depend on both the physical RAM you want to dedicate to > PostgreSQL and the nature and size of the database, then we have achieved > a medium revolution in computer science. ;-) But this is not about "optimal" settings. This is about "pretty good" settings. As long as we can get past the knee of the performance curve, I think we've done what should be expected of a default parameter set. I believe that 1000 buffers is enough to get past the knee in most scenarios. Again, I haven't got hard evidence, but that's my best guess. regards, tom lane