| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | pgpool-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Proposal: change log_pcp_processes default to off |
| Date: | 2025-08-15 02:11:00 |
| Message-ID: | 20250815.111100.2261166502134199972.ishii@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bo Peng | 2025-08-15 02:25:01 | Re: Proposal: change log_pcp_processes default to off |
| Previous Message | Tatsuo Ishii | 2025-08-13 11:10:58 | Re: Proposal: emit warning if life check has not started yet |