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

From: Darren Duncan <darren(at)darrenduncan(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL command to edit postgresql.conf, with comments
Date: 2010-10-12 22:34:42
Message-ID: 4CB4E282.2050505@darrenduncan.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus wrote:
>> The fact that Postgres already
>> explicitly supports comment metadata in its system catalog means it must
>> already know something about this.
>
> We support what?

Postgres has "COMMENT ON ..." SQL for various database objects and I assumed
that said comments would be stored in the system catalog.

http://www.postgresql.org/docs/9.0/interactive/sql-comment.html

> The solution to this is simple, and was previously discussed on this list:
>
> (a) have a postgresql.conf.auto
> (b) add a default include for postgresql.conf.auto at the beginning of
> PostgreSQL.conf
> (c) SQL updates go to postgresql.conf.auto, which consists only of
> "setting = value" in alphabetical order.
> (d) We document that settings which are changed manually in
> postgresql.conf will override postgresql.conf.auto.
> (e) $$profit$$!!

I agree that this looks like an effective solution.

-- Darren Duncan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2010-10-12 22:36:30 Re: Review: Fix snapshot taking inconsistencies
Previous Message Neil Whelchel 2010-10-12 22:33:33 Re: Slow count(*) again...