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

From Amit Kapila
Subject Re: postgresql.auto.conf and reload
Date
Msg-id CAA4eK1K2y1FN_xiZpOM_JQbb2aqqXU62JKAPTiqGhJ4w75LoRg@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 Wed, Jun 25, 2014 at 7:45 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Wed, Jun 25, 2014 at 6:47 PM, Christoph Berg <cb@df7cb.de> wrote:
> > Re: Amit Kapila 2014-06-25 <CAA4eK1Log98jvFOV9wzTqpCdEWJa+5JR54TTpkiZ3XBnGJydLA@mail.gmail.com>
> > > This will happen without Alter System as well, if you change
> > > the value of port in postgresql.conf and try to load conf file with SIGHUP.
> > > You cannot reload PGC_POSTMASTER parameters without server restart.
> >
> > That's not the issue. I did restart the server, which didn't log any
> > problems, yet reload keeps complaining indefinitely. This makes ALTER
> > SYSTEM not-so-nice-to-use to override parameters already set in
> > postgresql.conf.
>
> The main reason behind such such a behaviour after restart is
> that there are duplicate entries, one in postgresql.conf and
> another in postgresql.conf.  

Sorry, I mean to say one in postgresql.conf and another in
postgresql.auto.conf

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: Christoph Berg
Date:
Subject: Re: postgresql.auto.conf and reload