On Jun 6, 2008, at 01:50, Andreas Pflug wrote:
Two heretical questions:
Do we need user generated comments at all?
I can't remember ever having used any comment in postgresql.conf.
That's a valid point. I've used comments to note by whom and when when
a setting was changed.
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?
I think that there has been enough pushback against housing all the
settings in the database, not to mention that it calls for an API,
that just starting with something simpler to parse the file and
rewrite it from the command-line might be a better first step.
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").
I think the first option there is the one that's been getting the most
support here.
Best,
David
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
