mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: mention pg_reload_conf() for reloading the config file

Browse Source 
Reported-by: Ian Barwick

Discussion: https://postgr.es/m/538950ec-b86a-1650-6078-beb7091c09c2@2ndquadrant.com

Backpatch-through: 9.4
This commit is contained in:
Bruce Momjian 2019-07-15 20:57:24 -04:00
parent f757d89e88
commit c83067d7ea
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/client-auth.sgml
View File

@ -603,8 +603,9 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
<systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm> <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
signal. If you edit the file on an signal. If you edit the file on an
active system, you will need to signal the postmaster active system, you will need to signal the postmaster
(using <literal>pg_ctl reload</literal> or <literal>kill -HUP</literal>) to make it (using <literal>pg_ctl reload</literal>, calling the SQL function
re-read the file. <function>pg_reload_conf()</function>, or using <literal>kill
-HUP</literal>) to make it re-read the file.
</para> </para>
<note> <note>
@ -821,8 +822,9 @@ mymap /^(.*)@otherdomain\.com$ guest
<systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm> <systemitem>SIGHUP</systemitem><indexterm><primary>SIGHUP</primary></indexterm>
signal. If you edit the file on an signal. If you edit the file on an
active system, you will need to signal the postmaster active system, you will need to signal the postmaster
(using <literal>pg_ctl reload</literal> or <literal>kill -HUP</literal>) to make it (using <literal>pg_ctl reload</literal>, calling the SQL function
re-read the file. <function>pg_reload_conf()</function>, or using <literal>kill
-HUP</literal>) to make it re-read the file.
</para> </para>
<para> <para>