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

help / color / mirror / Atom feed
From: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Fri, 06 Jun 2008 10:51:50 +0200
Message-ID: <4848FAA6.8000903@pse-consulting.de> (raw)
In-Reply-To: <3F927D52-A0FD-4575-8D24-F0F70C459235@kineticode.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>

David E. Wheeler wrote:
>
> How about a simple rule, such as that machine-generated comments start 
> with "##", while user comments start with just "#"? I think that I've 
> seen such a rule used before. At any rate, I think that, unless you 
> have some sort of line marker for machine-generated comments, there 
> will be no way to tell them apart from user comments. 

Two heretical questions:
Do we need user generated comments at all?
I can't remember ever having used any comment in postgresql.conf.

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?


Looking around for different approaches, network appliances come to my 
mind, e.g. Cisco routers and PIX. You have 3 ways to configure a pix:
- use a command line (using ssh or telnet, eqivalent to psql); WRITE 
MEMORY to make the changes survive a reboot.
- use a web interface (or similar tool)
- use tftp to up/download the complete config in and out, editing the 
file. User comments will be lost, with the exception of those that have 
been applied with special comment commands (equivalent to "comment on").



Regards,
Andreas





view thread (226+ messages)  latest in thread

Message-ID: <4848FAA6.8000903@pse-consulting.de>
Permalink:  ../4848FAA6.8000903@pse-consulting.de/
Also on:    postgresql.org/message-id/4848FAA6.8000903@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
  Subject: Re: Overhauling GUCS
  In-Reply-To: <4848FAA6.8000903@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