Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z4fSX-0004lY-4q for pgsql-docs@arkaria.postgresql.org; Tue, 16 Jun 2015 01:14:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Z4fSW-0004Eg-3H for pgsql-docs@arkaria.postgresql.org; Tue, 16 Jun 2015 01:14:36 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Z4fSV-0004EZ-7M for pgsql-docs@postgresql.org; Tue, 16 Jun 2015 01:14:35 +0000 Received: from smtp-auth.no-ip.com ([8.23.224.61] helo=out.smtp-auth.no-ip.com) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z4fSP-0002aK-TZ for pgsql-docs@postgresql.org; Tue, 16 Jun 2015 01:14:34 +0000 X-No-IP: alvh.no-ip.org@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from alvin.alvh.no-ip.org (unknown [216.13.52.59]) (Authenticated sender: alvh.no-ip.org@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 1031D40110D; Mon, 15 Jun 2015 18:14:22 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id E8AE62955; Mon, 15 Jun 2015 22:14:20 -0300 (CLT) Date: Mon, 15 Jun 2015 22:14:20 -0300 From: Alvaro Herrera To: "David G. Johnston" Cc: Euler Taveira , Jeff Janes , "pgsql-docs@postgresql.org" Subject: Re: "Alter system" command documentation Message-ID: <20150616011420.GP133018@postgresql.org> References: <557F3C7C.2010802@timbira.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org David G. Johnston wrote: > On Mon, Jun 15, 2015 at 4:58 PM, Euler Taveira wrote: > > > On 15-06-2015 13:32, Jeff Janes wrote: > > > 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. > > I disagree on SIGHUP being an implementation detail. Using signals in > IPC (inter-process communication) is a public API that should be > documented when applicable. Agreed. However, I don't think it makes sense to document that either SIGHUP, pg_ctl reload, and pg_reload_conf() can be used whenever a parameter reload is mentioned; that would bloat too much (in a quick grep, I see at least 10-15 places where SIGHUP or "reload" is mentioned in the context of config files.) Maybe we should have one section somewhere, saying "reload is executed by any of the following:" and list them all. Then this place and others could simply say "these values are effective after reload, about which see section X.Y.Z". -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs