Message-ID: <1412139392.13055.2.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: Jason Mathis <jmathis@redzonesoftware.com>
Cc: Ian Barwick <ian@2ndquadrant.com>, Strahinja =?UTF-8?Q?Kustudi=C4=87?=
 <strahinjak@nordeus.com>, "pgsql-admin@postgresql.org"
 <pgsql-admin@postgresql.org>
Date: Wed, 01 Oct 2014 00:56:32 -0400
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>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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