Horton

Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndQuadrant.com>
To: Amit Kapila <amit.kapila@huawei.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Magnus Hagander <magnus@hagander.net>, Peter Eisentraut <peter_e@gmx.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Josh Berkus <josh@agliodbs.com>
Date: 2013-07-03T12:59:15Z
Lists: pgsql-hackers 
On 3 July 2013 07:45, Amit Kapila <amit.kapila@huawei.com> wrote:


> > postgresql.auto.conf is similar enough to postgresql.conf that it will
> prevent tab completion from working as it does now. As a result it will
> cause
> > people to bring that file up for editing when we wish to avoid that.
>
>   This new file postgresql.auto.conf will be created inside a new directory
> "config", so both will be in different directories.
>   Will there be any confusion with tab completion for different
> directories?


Tab completion will not be confused, no.

But I think everything else will be. How will I know that some settings
have been set by ALTER SYSTEM and some by other means?


Sounds to me like a recipe for chaos. I hope nobody is calling for a commit
on this anytime soon. I think the whole thing needs some careful thought
and review before we commit this.

 --
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services