Message-ID: <4849137C.3040008@pse-consulting.de>
Date: Fri, 06 Jun 2008 12:37:48 +0200
From: Andreas Pflug <pgadmin@pse-consulting.de>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Gregory Stark <stark@enterprisedb.com>
CC: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
References: <Pine.GSO.4.64.0806041045520.2258@westnet.com>
	<29525.1212613052@sss.pgh.pa.us>
	<48472E47.7030701@dunslane.net>
	<Pine.GSO.4.64.0806042033120.3874@westnet.com>
	<20080605162400.GF16502@alvh.no-ip.org>	<48481CBF.6040602@enterprisedb.com>
	<48481E3A.4010306@hagander.net>
	<Pine.GSO.4.64.0806051321360.27711@westnet.com>
	<20080605174209.GL16502@alvh.no-ip.org>
	<Pine.GSO.4.64.0806051452480.27254@westnet.com>
	<20080605212129.GI14498@yugib.highrise.ca>
	<Pine.GSO.4.64.0806051725550.10475@westnet.com>
	<3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.com>
	<4848FAA6.8000903@pse-consulting.de>
	<87ej7aeuqx.fsf@oxford.xeocode.com>
In-Reply-To: <87ej7aeuqx.fsf@oxford.xeocode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Gregory Stark wrote:
> "Andreas Pflug" <pgadmin@pse-consulting.de> writes:
>
>   
>> Why do so many people here insist on editing postgresql.conf as primary means
>> of changing config params?
>> Isn't a psql -c "SET foo=bar; MAKE PERSISTENT" just as good as sed'ing
>> postgresql.conf or doing it manually?
>>     
>
> no, it's awful.
>
>   

So I wonder why you accept it when configuring schemas. What's the big 
difference between setting a config param, and creating a table?

And ultimately, the config param file format may well look like an SQL 
command file, restricted to SET only.


> And in every major installation I've seen people use the last option. They
> treat the original text file which is kept elsewhere -- normally checked into
> some revision control system, tracked and managed like source code -- as the
> canonical and authoritative version.
>   

That's how you'd have to manage the schema sources too, no? Your 
comments are lost as well after schema creation scripts are executed, 
and manual changes may interfere with that.

Regards,
Andreas