Horton

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

Andres Freund <andres@2ndquadrant.com>

View thread View on postgr.es
From: Andres Freund <andres@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>, Dimitri Fontaine <dimitri@2ndQuadrant.fr>, David Johnston <polobo@yahoo.com>, pgsql-hackers@postgresql.org, Amit Kapila <amit.kapila@huawei.com>, Gregory Stark <gsstark@mit.edu>
Date: 2013-08-02T00:40:51Z
Lists: pgsql-hackers 
On 2013-08-01 20:33:49 -0400, Stephen Frost wrote:
> * Andres Freund (andres@2ndquadrant.com) wrote:
> > People know what to expect from .d directories, that's why I suggested
> > it, don't feel really strongly about it. I dislike naming the
> > subdirectories pgconf/... et al though, we should reference the original
> > files name, instead of introducing new abbreviations.
> 
> *People* should not be messing around with files under $PGDATA- that's
> half the point.  conf.d or other names which look like configuration
> directories that an admin should modify are a *bad* idea.

I personally consider readers of this list persons... And even people
not interested in internals will have to look in there if they set
something stupid before. Like setting max_connections higher than the
currently configured kernel's max number of semaphores. Or a good number
of other settings.

Greetings,

Andres Freund

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