Re: postgresql.auto.conf and reload

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgresql.auto.conf and reload
Date: 2014-07-26 04:07:26
Message-ID: CAA4eK1LREecO8kUZFb9bzvLPWBDCvRbtyggu0CykA=pQHCnAgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 25, 2014 at 6:11 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Jul 9, 2014 at 11:05 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
> > Okay. As mentioned upthread, I have fixed by ensuring that for duplicate
> > config params, retain only which comes later during parsing.
> > I think it might have been bit simpler to fix, if we try to fix after
> > parsing
> > is complete, but I think for that we might need to replicate the logic
> > at multiple places.
>
> ISTM that the patch works fine. Only concern is that the logic needs
> O(n^2) comparison, which may cause performance problem. But
> "n" in O(n^2) is the number of uncommented parameters and I don't
> think it's so big, ISTM I can live with the logic...

Thanks for reviewing the patch. I also think that having O(n^2)
comparisons should not be a problem in this logic as it will be processed
only during load/parse of config file which we don't do in performance
sensitive path.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2014-07-26 06:23:08 Re: Use unique index for longer pathkeys.
Previous Message Peter Eisentraut 2014-07-26 03:41:37 Re: PDF builds broken again