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

Re: Overhauling GUCS

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
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 20:00:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Jun 4, 2008, at 12:48, Andrew Dunstan wrote:

>> 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.

I didn't say it was better. The point is that it seems to be less  
confusing to non-DBAs.

>> 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.

Agreed; we've bandied around some better ideas here. Well, I haven't,  
I've just kibbitzed. But we can surely do better.



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-06-04 20:12:05
Subject: Re: Overhauling GUCS
Previous:From: Andrew DunstanDate: 2008-06-04 19:48:47
Subject: Re: Overhauling GUCS

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