Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Date
Msg-id 20140116133423.GW2686@tamriel.snowman.net
Whole thread Raw
In response to Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Peter,

* Peter Eisentraut (peter_e@gmx.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.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Jeevan Chalke
Date:
Subject: Re: [PATCH] Filter error log statements by sqlstate
Next
From: Andres Freund
Date:
Subject: Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it