Re: postgresql.auto.conf and reload - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: postgresql.auto.conf and reload
Date
Msg-id CAA4eK1KwGRt_EjA1ekY4GNWadMrCP-r2BAssQUD48mFbqzqe5A@mail.gmail.com
Whole thread Raw
In response to Re: postgresql.auto.conf and reload  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Sun, Aug 10, 2014 at 12:24 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Fri, Aug 8, 2014 at 11:41 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> >
> > Yep, right. ParseConfigFp() is not good place to pick up data_directory.
> > What about the attached patch which makes ProcessConfigFile() instead of
> > ParseConfigFp() pick up data_directory just after the configuration file is
> > parsed?
>
> I think this is better way to handle it. Few comments about patch:
>
> 1. can't we directly have the code by having else in below loop.
> if (DataDir &&
> !ParseConfigFile(PG_AUTOCONF_FILENAME, NULL, false, 0, elevel,
> &head, &tail))

I think for this we need to change the above condition a bit.


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

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: postgresql.auto.conf and reload
Next
From: Andres Freund
Date:
Subject: Re: Reporting the commit LSN at commit time