Re: SQL command to edit postgresql.conf, with comments

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Darren Duncan <darren(at)darrenduncan(dot)net>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL command to edit postgresql.conf, with comments
Date: 2010-10-14 16:40:58
Message-ID: 4CB7329A.3070700@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> Sure. I just lose comments. I'll live with that.

Actually, as part of this scheme, it would be nice if pg_settings had a
"comment" column, which would be optionally set with SET PERMANENT. Not
required, but nice to have.

If we had that, I suspect that a lot fewer people would want a
hand-edited file.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-10-14 16:41:04 Re: [GENERAL] pg_filedump binary for CentOS
Previous Message Bernd Helmle 2010-10-14 16:40:56 Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch