From: Peter Eisentraut <peter_e@gmx.net>
To: Jason Mathis <jmathis@redzonesoftware.com>
Cc: Ian Barwick <ian@2ndquadrant.com>
Cc: Strahinja Kustudić <strahinjak@nordeus.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: How to detect if Postgres needs a restart when configuration changes
Date: Wed, 01 Oct 2014 00:56:32 -0400
Message-ID: <1412139392.13055.2.camel@vanquo.pezone.net> (raw)
In-Reply-To: <7090DAD0-F2CA-4574-9CA0-BBDF6DD85A04@redzonesoftware.com>
References: <CADKbJJVwK9Gx=UEAZQthz-_6kOOcd36_qnyX0+R9StD4bmcH6w@mail.gmail.com>
<542B48C5.6070507@2ndquadrant.com>
<7090DAD0-F2CA-4574-9CA0-BBDF6DD85A04@redzonesoftware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On Tue, 2014-09-30 at 18:51 -0600, Jason Mathis wrote:
> How are you automating? Have you looked at puppet or anything? Puppet
> labs maintains a postgresql module that has all that baked in. Check
> it out at least it can give you some ideas.
Their "idea" is to maintain a hard-coded list about which parameter
changes need a restart, and their list is wrong.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter_e@gmx.net, jmathis@redzonesoftware.com, ian@2ndquadrant.com, strahinjak@nordeus.com
Subject: Re: How to detect if Postgres needs a restart when configuration changes
In-Reply-To: <1412139392.13055.2.camel@vanquo.pezone.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox