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

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, 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:36:49
Message-ID: CAA4eK1K3ByP0z+6rxZ5uHvxc75HdHhicmUZ4-mokf0CSnLqPwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 16, 2014 at 1:31 AM, Josh Berkus <josh(at)agliodbs(dot)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

In response to

Browse pgsql-hackers by date

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