Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Amit Kapila <amit.kapila@huawei.com>
From: Amit Kapila <amit.kapila@huawei.com>
To: "'Simon Riggs'" <simon@2ndQuadrant.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-03T13:29:31Z
Lists: pgsql-hackers
On Wednesday, July 03, 2013 6:29 PM Simon Riggs wrote: 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? Other means by hand editing postgresql.auto.conf? If not we can check in pg_settings, it shows sourcefile. So if the setting is from new file postgresql.auto.conf, this means it is set by ALTER SYSTEM. With Regards, Amit Kapila.