Re: Proposal: change log_pcp_processes default to off

Ishii-san,

> So I propose to change the default of log_pcp_processes to off.

I agree with your proposal.

---
Bo Peng <pengbo(at)sraoss(dot)co(dot)jp>
SRA OSS K.K.
TEL: 03-5979-2701 FAX: 03-5979-2702
Mobile: 080-7752-0749
URL: https://www.sraoss.co.jp/

________________________________________
差出人: Tatsuo Ishii <ishii(at)postgresql(dot)org>
送信: 2025 年 8 月 15 日 (金曜日) 11:11
宛先: pgpool-hackers(at)lists(dot)postgresql(dot)org <pgpool-hackers(at)lists(dot)postgresql(dot)org>
件名: Proposal: change log_pcp_processes default to off

log_pcp_processes logs something like:

2025-08-14 16:17:14.899: pcp_main pid 40704: LOG:  forked new pcp worker, pid=41021 socket=7
2025-08-14 16:17:14.904: pcp_main pid 40704: LOG:  PCP process with pid: 41021 exit with SUCCESS.
2025-08-14 16:17:14.904: pcp_main pid 40704: LOG:  PCP process with pid: 41021 exits with status 0

They are printed every time a pcp command is invoked. If admins use
pcp command frequently to monitor pgpool status, it's annoying because
the log file is flooded by these messages. Even if they can be turned
off by setting log_pcp_processes to off, I think it should be
defaulted to off because they are kind of debugging message.

So I propose to change the default of log_pcp_processes to off.

Best regards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp