Message-ID: <1412139303.13055.0.camel@vanquo.pezone.net>
Subject: Re: How to detect if Postgres needs a restart when
 configuration changes
From: Peter Eisentraut <peter_e@gmx.net>
To: Strahinja =?UTF-8?Q?Kustudi=C4=87?= <strahinjak@nordeus.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Date: Wed, 01 Oct 2014 00:55:03 -0400
In-Reply-To: 
 <CADKbJJVwK9Gx=UEAZQthz-_6kOOcd36_qnyX0+R9StD4bmcH6w@mail.gmail.com>
References: 
 <CADKbJJVwK9Gx=UEAZQthz-_6kOOcd36_qnyX0+R9StD4bmcH6w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Wed, 2014-10-01 at 01:51 +0200, Strahinja Kustudi=C4=87 wrote:
> I am automating Postgres deployment on Linux and I need to check if
> Postgres needs to be restarted when a configuration parameter that
> requires a restart changes, e.g. when you change wal_level. Is there a
> way to detect a parameter which requires a restart was changed?

As you can gather, there isn't really a straightforward way.  But it
would be a great feature addition.


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin