Re: [HACKERS] Should we eliminate or reduce HUP from docs? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Should we eliminate or reduce HUP from docs?
Date
Msg-id 20170316133123.GA19128@momjian.us
Whole thread Raw
In response to [HACKERS] Should we eliminate or reduce HUP from docs?  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Fri, Mar 10, 2017 at 11:57:30AM -0800, Joshua Drake wrote:
> Hello,
> 
> I am a bad speaker, I am writing a talk three weeks before the conference
> (as opposed to on the plane). I noticed in the docs we still reference the
> passing of SIGHUP for reloading conf file but we now have pg_reload_conf();
> 
> It seems the use of pg_reload_conf() would provide a better canonical
> interface to our users. Especially those users who are not used to
> interacting with the OS (Windows, Oracle etc...) for databases.

FYI, I did apply this patch for PG 10:
commit 10c064ce4dad088ba2d8b978bff6009b9f22dc3aAuthor: Bruce Momjian <bruce@momjian.us>Date:   Tue Oct 25 11:26:15 2016
-0400   Consistently mention 'SELECT pg_reload_conf()' in config files    Previously we only mentioned SIGHUP and
'pg_ctlreload' in    postgresql.conf and pg_hba.conf.
 

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] logical replication launcher crash on buildfarm
Next
From: "Daniel Verite"
Date:
Subject: Re: [HACKERS] PATCH: Batch/pipelining support for libpq