Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Amit Kapila <amit.kapila@huawei.com>, Boszormenyi Zoltan <zb@cybertec.at>, pgsql-hackers@postgresql.org
Date: 2013-01-26T17:01:59Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 24, 2013 at 12:39 PM, 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.

IMO an include directory containing just one file is silly.  If we're
going with the single-file approach, let's lose the directory altogether
and just store the file at $PGDATA/postgresql.conf.auto.

			regards, tom lane