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

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> But creating a separate file doesn't fix that problem. It just moves
> it around. If people will expect comments in postgresql.conf to get
> preserved, then why won't they also expect comments in
> postgresql.conf.auto to get preserved?

Because postgresql.conf.auto will have a nice leading comment telling
people (1) not to hand-edit the file, (2) if they do so anyway,
not to expect comments to be preserved, and (3) the place to do manual
editing of settings is postgresql.conf.

> If the answer is "because postgresql.conf has always worked that way
> before", then add one more line to the proposed initial contents
> saying it's not true any more.

Sorry, wrong answer. The objection to this is not whether you tell
people that you're taking away the ability to keep useful comments
in postgresql.conf, it's that you're taking away the ability.

regards, tom lane