Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgpool-hackers-owner+archive@lists.postgresql.org>)
	id 1umjuY-002sVJ-OW
	for pgpool-hackers@arkaria.postgresql.org; Fri, 15 Aug 2025 02:11:19 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgpool-hackers-owner+archive@lists.postgresql.org>)
	id 1umjuX-00BTgP-93
	for pgpool-hackers@arkaria.postgresql.org; Fri, 15 Aug 2025 02:11:17 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <ishii@postgresql.org>)
	id 1umjuX-00BTet-3F
	for pgpool-hackers@lists.postgresql.org; Fri, 15 Aug 2025 02:11:17 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <ishii@postgresql.org>)
	id 1umjuT-000dvd-1j
	for pgpool-hackers@lists.postgresql.org;
	Fri, 15 Aug 2025 02:11:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type:
	Mime-Version:From:Subject:To:Message-Id:Date:Sender:Reply-To:Cc:Content-ID:
	Content-Description:In-Reply-To:References;
	bh=gEJ056DMb2Wq7U2rfdR+yoPP+ChYyWhOAsQ8ER3v4ps=; b=VxOgXPI73JXk3WuuNXKEVCVdaU
	ZIoao9woddAEfM0WZSBk10cty5iT8MQJe7vny5+QMG9euziePdM8Y39jG73zNKl09ucQUMjJftDtA
	y/YjK/KFfPueyrxtSqAN4vk5grRfxN5KT0H5dPEkb15AL2rj96uDHzHgofV6Et/CeEPb89oEbHGm8
	S9TqypDQeBAZMzulzFUDpIsCUSVZ9ePGW0knKwks7Xigx+N4ZUEFR8DkhX7nlbjZz76E6G1bzYbNn
	whjEMhiVxx7DWhgR4zsS+u+kjySIVezwJnBImSHe3xgQo+VBfS7OjHLVWDOz6uwyxkw3WFyz0fCjm
	Aeg9iW0Q==;
Received: from [2409:11:4120:300:a2f8:c27c:9a6e:c091] (helo=localhost)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
	(Exim 4.96)
	(envelope-from <ishii@postgresql.org>)
	id 1umjuO-001gjP-2q
	for pgpool-hackers@lists.postgresql.org;
	Fri, 15 Aug 2025 02:11:12 +0000
Date: Fri, 15 Aug 2025 11:11:00 +0900 (JST)
Message-Id: <20250815.111100.2261166502134199972.ishii@postgresql.org>
To: pgpool-hackers@lists.postgresql.org
Subject: Proposal: change log_pcp_processes default to off
From: Tatsuo Ishii <ishii@postgresql.org>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Host-Lookup-Failed: Reverse DNS lookup failed for
 2409:11:4120:300:a2f8:c27c:9a6e:c091 (failed)
List-Id: <pgpool-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgpool-hackers@lists.postgresql.org>
List-Owner: <mailto:pgpool-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgpool-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/20250815.111100.2261166502134199972.ishii%40postgresql.org>
Precedence: bulk

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