Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]

Robert Haas <robertmhaas@gmail.com> wrote:
> Andres Freund <andres@2ndquadrant.com> wrote:
>> More people seem to have voted for the single file approach but I still
>> haven't understood why...
>
> Me neither.  Having an include directory seems good, but I can't think
> why we'd want to clutter it up with a bajillion automatically
> generated files.  One .auto file that gets overwritten at need seems
> way nicer.

The single-value per file approach punts the concurrency issues and
ordering issues to the OS, which might significantly simplify the
patch.  I'm not sure that the niceness of the all-in-one-file
approach justifies the extra code.  If you ever want to view them
all in one file as of some moment in time, there is always:

  cat * | less

-Kevin