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

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: 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:34:23
Message-ID: 20140116133423.GW2686@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-01-16 13:58:06 Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Previous Message Jeevan Chalke 2014-01-16 13:22:15 Re: [PATCH] Filter error log statements by sqlstate