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

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: 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 05:54:47
Message-ID: 52D77427.6000001@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 01/16/2014 02:53 AM, Josh Berkus wrote:
> Hackers,
>
> ALTER SYSTEM SET has been committed and recovery.conf GUCs are being
> reviewed. I'm going to make a last case for conf.d in relation to these
> two patches before 9.4 goes out the door.

Personally, I'd find conf.d greatly more useful when enabled by default.
The need to hack postgresql.conf to use it eliminates half the point of
having it.

I haven't seen any compelling reason why conf.d should NOT be enabled by
default.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2014-01-16 06:39:07 Re: [PATCH] Negative Transition Aggregate Functions (WIP)
Previous Message Amit Kapila 2014-01-16 05:36:49 Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it