Message-ID: <557F3C7C.2010802@timbira.com.br>
Date: Mon, 15 Jun 2015 17:58:36 -0300
From: Euler Taveira <euler@timbira.com.br>
Organization: Timbira
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.7.0
MIME-Version: 1.0
To: Jeff Janes <jeff.janes@gmail.com>, pgsql-docs@postgresql.org
Subject: Re: "Alter system" command documentation
References: 
 <CAMkU=1xjSYan=T518E+=J4Ugg8xkymjx5a_hSFx1roB-chKyxw@mail.gmail.com>
In-Reply-To: 
 <CAMkU=1xjSYan=T518E+=J4Ugg8xkymjx5a_hSFx1roB-chKyxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On 15-06-2015 13:32, Jeff Janes wrote:
> From http://www.postgresql.org/docs/current/static/sql-altersystem.html
> 
> "Values set with ALTER SYSTEM will be effective after the next server
> configuration reload (SIGHUP or pg_ctl reload), or after the next server
> restart in the case of parameters that can only be changed at server start."
> 
> Isn't it unfortunate that the command used for changing the
> configuration file from within SQL mentions SIGHUP and pg_ctl reload,
> but not "select pg_reload_conf();", as a way to activate that change?  
> 
SIGHUP is an implementation detail. If I were to change that sentence,
my preference is replace SIGHUP with pg_reload_conf.


-- 
   Euler Taveira                   Timbira - http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento


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