pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Gregory Stark <stark@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Fri, 06 Jun 2008 12:37:48 +0200
Message-ID: <4849137C.3040008@pse-consulting.de> (raw)
In-Reply-To: <87ej7aeuqx.fsf@oxford.xeocode.com>
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>

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






view thread (226+ messages)  latest in thread

Message-ID: <4849137C.3040008@pse-consulting.de>
Permalink:  ../4849137C.3040008@pse-consulting.de/
Also on:    postgresql.org/message-id/4849137C.3040008@pse-consulting.de

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pgadmin@pse-consulting.de, stark@enterprisedb.com
  Subject: Re: Overhauling GUCS
  In-Reply-To: <4849137C.3040008@pse-consulting.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox