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

From Andres Freund
Subject Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Date
Msg-id 20130801172443.GP19053@alap2.anarazel.de
Whole thread Raw
In response to Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 2013-08-01 10:16:59 -0700, Josh Berkus wrote:
> Dimitri,
> 
> > We rehash because the situation did change *a lot*. We just decided that
> > the ALTER SYSTEM SET setup will live in PGDATA and will not have to be
> > edited by DBA nor sysadmin nor tools ever. We will have a separate
> > facility (conf.d) for that. As a result, I don't think there's any
> > issues left with one-setting-per-file now.
> 
> Let's please NOT call it conf.d if it's living in PGDATA and is not
> meant to be edited by hand.  conf.d is for a directory of config files
> created by users and external utilities, living in CONFIGDIR.

How nice that that's not what's being discussed here then. conf.d *IS*
the thing thats been proposed to be a separate feature from ALTER
SYSTEM. For the use case you describe.

Greetings,

Andres Freund

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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Alvaro Herrera
Date:
Subject: Re: libpq thread locking during SSL connection start