Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 324BA2E002F for ; Wed, 4 Jun 2008 16:49:10 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 24653-09 for ; Wed, 4 Jun 2008 16:49:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by developer.postgresql.org (Postfix) with ESMTP id 54FE42E002E for ; Wed, 4 Jun 2008 16:49:05 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-177-228.nc.res.rr.com [::ffff:75.177.177.228]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Wed, 04 Jun 2008 15:48:09 -0400 id 00097B96.4846F17A.00000BAF Message-ID: <4846F19F.7060408@dunslane.net> Date: Wed, 04 Jun 2008 15:48:47 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: "David E. Wheeler" CC: Tom Lane , Greg Smith , Josh Berkus , pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS References: <48409D1E.3070208@agliodbs.com> <484418D9.5040608@sun.com> <200806021106.05833.josh@agliodbs.com> <0B854D92-C5C2-4138-A0FE-F81892A33869@sun.com> <72DA5875-8E89-4A6F-8D0B-7F9A869D79B9@kineticode.com> <27574.1212603758@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/169 X-Sequence-Number: 119282 David E. Wheeler wrote: > On Jun 4, 2008, at 11:22, Tom Lane wrote: > >> "David E. Wheeler" writes: >>> Exactly. The issue is that application developers, who are not DBAs, >>> have no idea how to tune PostgreSQL, and postgresql.conf is daunting >>> and confusing. So they use a different database that's "faster". >> >> I take it you haven't looked at mysql's configuration file lately. > > I'm not much into MySQL, but in the work I've done with it, I've had > to create /etc/my.cnf myself. There *is* no configuration file > configuring MySQL until that file is created, is there? So there is no > configuration to learn at first. I'm not saying that this is > necessarily admirable -- it's kind of the opposite end of the spectrum > (PostgreSQL: "Here is every configuration tweak you could ever > possibly want, have fun!" vs MySQL: "There is no configuration until > you need one, then you have to find the docs for it." Tell me how that's better. If that's what you want, simply remove all the comment lines from your config file. Problem solved. > >> They aren't actually in any better shape than we are, except that >> they supply several "preconfigured" sample files for people to choose >> from. > > Which would be a good start, if nothing else… It's been suggested in the past. It is highly debatable that it would actually be an advance. cheers andrew