Postgres Pro
Downloads
Home   >   mailing lists

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

From Amit Kapila
Subject Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it
Date
Msg-id CAA4eK1K3ByP0z+6rxZ5uHvxc75HdHhicmUZ4-mokf0CSnLqPwA@mail.gmail.com
Whole thread Raw
In response to Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Tree view 
On Thu, Jan 16, 2014 at 1:31 AM, Josh Berkus <josh@agliodbs.com> wrote:
> On 01/15/2014 11:10 AM, Stephen Frost wrote:
>
>> Independent of the above, I don't agree with that.  postgresql.auto.conf
>> is a special thing and should have its own special place.  For once
>> thing, when putting configuration files in a separate directory
>> structure (/etc/ vs /var), then postgresql.auto.conf should stay in the
>> data directory.
>
> Ah, I'd forgotten about that line of argument.  Where is auto.conf now?
  Data Directory

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Asif Naeem
Date:
Subject: Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation
Next
From: Craig Ringer
Date:
Subject: Re: Why conf.d should be default, and auto.conf and recovery.conf should be in it