Previously log_pcp_processes default was on, and it could produce
excessive log lines if admins use pcp commands frequently to monitor
pgpool status. Also the log is kind of debugging message, thus it is
best to change its default value to off.
Discussion: https://www.postgresql.org/message-id/
20250815.111100.
2261166502134199972.ishii%40postgresql.org
Backpatch-through: master only
fork and exit status. Default is on.
-->
onに設定されている場合、PCPプロセスの正常なforkあるいはexitした状態をログに出力します。
- デフォルトはonです。
+ デフォルトはoffです。
</para>
<para>
<!--
<listitem>
<para>
Setting to on, enable logging about normal PCP Process
- fork and exit status. Default is on.
+ fork and exit status. Default is off.
</para>
<para>
This parameter can be changed by reloading the <productname>Pgpool-II</> configurations.
CONFIG_VAR_TYPE_BOOL, false, 0
},
&g_pool_config.log_pcp_processes,
- true,
+ false,
NULL, NULL, NULL
},
# Log connections
#log_disconnections = off
# Log disconnections
-#log_pcp_processes = on
+#log_pcp_processes = off
# Log PCP Processes
#log_hostname = off
# Hostname will be shown in ps status