X-Original-To: pgsql-hackers@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 86A14475925 for ; Tue, 11 Feb 2003 13:53:04 -0500 (EST) Received: from neuromancer.ctlno.com (unknown [208.13.35.90]) by postgresql.org (Postfix) with ESMTP id EB1A2475843 for ; Tue, 11 Feb 2003 13:53:03 -0500 (EST) Received: from [192.168.0.10] (ool-4352919e.dyn.optonline.net [67.82.145.158]) by neuromancer.ctlno.com (8.12.6/8.12.6) with ESMTP id h1BIYbv7009253; Tue, 11 Feb 2003 12:34:37 -0600 Subject: Re: Changing the default configuration (was Re: [pgsql-advocacy] From: "Matthew T. O'Connor" To: pgsql-hackers@postgresql.org, Tom Lane In-Reply-To: <26924.1044986473@sss.pgh.pa.us> References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <49391.192.168.1.12.1044985098.squirrel@mail.mayuli.com> <26924.1044986473@sss.pgh.pa.us> Content-Type: text/plain Organization: Message-Id: <1044989631.32185.151.camel@zeutrh80> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 (1.2.1-1) Date: 11 Feb 2003 13:53:51 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/409 X-Sequence-Number: 35351 On Tue, 2003-02-11 at 13:01, Tom Lane wrote: > "Jon Griffin" writes: > > So it appears that linux at least is way above your 8 meg point, unless I > > am missing something. > > Yeah, AFAIK all recent Linuxen are well above the range of parameters > that I was suggesting (and even if they weren't, Linux is particularly > easy to change the SHMMAX setting on). It's other Unixoid platforms > that are likely to have a problem. Particularly the ones where you > have to rebuild the kernel to change SHMMAX; people may be afraid to > do that. The issue as I see it is: Better performing vs. More Compatible Out of the box Defaults. Perhaps a compromise (hack?): Set the default to some default value that performs well, a value we all agree is not too big (16M? 32M?). On startup, if the OS can't give us what we want, instead of failing, we can try again with a smaller amount, perhaps half the default, if that fails try again with half until we reach some bottom threshold (1M?). The argument against this might be: When I set shared_buffers=X, I want X shared buffers. I don't want it to fail silently and give me less than what I need / want. To address this we might want to add a guc option that controls this behavior. So we ship postgresql.conf with 32M of shared memory and auto_shared_mem_reduction = true. With a comment that the administrator might want to turn this off for production. Thoughts? I think this will allow most uninformed users get decent performing defaults as most systems will accommodate this larger value.