Skip site navigation (1) Skip section navigation (2)

Re: Overhauling GUCS

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <gsmith(at)gregsmith(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Overhauling GUCS
Date: 2008-06-04 19:48:47
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

David E. Wheeler wrote:
> On Jun 4, 2008, at 11:22, Tom Lane wrote:
>> "David E. Wheeler" <david(at)kineticode(dot)com> 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.



In response to


pgsql-hackers by date

Next:From: David E. WheelerDate: 2008-06-04 20:00:02
Subject: Re: Overhauling GUCS
Previous:From: David E. WheelerDate: 2008-06-04 18:55:53
Subject: Re: Overhauling GUCS

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group