pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Greg Smith <gsmith@gregsmith.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: David E. Wheeler <david@kineticode.com>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Thu, 5 Jun 2008 20:53:16 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0806052029290.9064@westnet.com> (raw )
In-Reply-To: <20080606002452.GY16502@alvh.no-ip.org >
References: <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 >
<20080606002452.GY16502@alvh.no-ip.org >
On Thu, 5 Jun 2008, Alvaro Herrera wrote:
> FWIW smb.conf uses ; for one purpose and # for the other.
They're actually combining the way UNIX files use # with how Windows INI
files use ; in a config file context, which I personally find a little
weird.
I was already considering keeping user comments as # while making all
system-inserted ones #! ; many people are already used to #! having a
special system-related meaning from its use in UNIX shell scripting which
makes it easier to remember.
I think the next step to this whole plan is to generate a next-gen
postgresql.conf mock-up showing what each of the outputs from the
pg_generate_conf tool might look like to get feedback on that; it will
make what is planned here a bit easier to understand as well.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
view thread (226+ messages) latest in thread
Message-ID: <Pine.GSO.4.64.0806052029290.9064@westnet.com>
Permalink: ../Pine.GSO.4.64.0806052029290.9064@westnet.com/
Also on: postgresql.org/message-id/Pine.GSO.4.64.0806052029290.9064@westnet.com
copy link · copy postgr.es
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: gsmith@gregsmith.com, alvherre@commandprompt.com, david@kineticode.com, aidan@highrise.ca
Subject: Re: Overhauling GUCS
In-Reply-To: <Pine.GSO.4.64.0806052029290.9064@westnet.com>
* 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