Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Date: 2014-01-16 13:58:06
Message-ID: 20140116135505.GA4498@alap3.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-01-16 08:34:23 -0500, Stephen Frost wrote:
> Peter,
>
> * Peter Eisentraut (peter_e(at)gmx(dot)net) wrote:
> > Then one might as well argue that the pg_db_role_setting table be
> > relocated to /etc. It's the same facility, only on a slightly different
> > level. The fact that postgresql.auto.conf looks the same as a
> > plain-text configuration file is an implementation detail. We could
> > have chosen some binary format instead.
>
> I argued quite a bit that we should be looking at moving more things
> into the catalog tables and pulling them out of postgresql.conf,
> reducing that down to just what's required to be there, rather than this
> nasty hack where SQL commands are modifying text config files.

Given that the majority didn't seem to be convinced by this and that the
feature was written differently this isn't a convincing argument for the
location of the file given the current feature, no?

Greetings,

Andres Freund

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-01-16 14:06:30 Re: WAL Rate Limiting
Previous Message Stephen Frost 2014-01-16 13:34:23 Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it