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.96)
	(envelope-from <pgpool-hackers-owner+archive@lists.postgresql.org>)
	id 1vUlkO-007Ljm-2P
	for pgpool-hackers@arkaria.postgresql.org;
	Sun, 14 Dec 2025 13:02:49 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgpool-hackers-owner+archive@lists.postgresql.org>)
	id 1vUlkN-00CxwB-1S
	for pgpool-hackers@arkaria.postgresql.org;
	Sun, 14 Dec 2025 13:02:48 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <ishii@postgresql.org>)
	id 1vUlkN-00Cxw4-0i
	for pgpool-hackers@lists.postgresql.org;
	Sun, 14 Dec 2025 13:02:48 +0000
Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <ishii@postgresql.org>)
	id 1vUlkL-000gqX-0J
	for pgpool-hackers@lists.postgresql.org;
	Sun, 14 Dec 2025 13:02:47 +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=HUcCJ+Dkyeu0LVNBRX7QZVEFdRYkZ6/X6uGfPZaK4ME=; b=UGyidl1zdL/7KohKd5SOOLcP32
	8IDpK0N8zr5DzNxSPd5e96O+xFPFCg4adHNI44/RXJ4+PiEA1Ic40TJenGSVgyoWAjvUdR9rW3x91
	dtwp+cz8YcG6+RKvNm5IN9hGKtL7HlPkuCi4r4KotTq4yVOajDnpVkUforTxBPKAPmvSLWU+3fZjT
	b7pBfNRpdfRExq7//BvH4GfJh6HivtW5sRygf5SB4p7HcpzHC03Ju1k5nZ0cQ1qKJiBXo+AdGJaAZ
	1ZYdsKCsFC/j33lEnNTFhCCOFP4vEP5PX9o98J6XCgmD2OnADKSbiGC0NslEEfZhWVj93u0+tTzUR
	fos//4+g==;
Received: from [2409:11:4120:300:6cdc:6925:b924:ca8c] (helo=localhost)
	by meldrar.postgresql.org with esmtpsa  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <ishii@postgresql.org>)
	id 1vUlkH-001F97-12
	for pgpool-hackers@lists.postgresql.org;
	Sun, 14 Dec 2025 13:02:43 +0000
Date: Sun, 14 Dec 2025 22:02:31 +0900 (JST)
Message-Id: <20251214.220231.820411055090373414.ishii@postgresql.org>
To: pgpool-hackers@lists.postgresql.org
Subject: Feature: add sync message logging to log_per_node_statement and
 notice_per_node_statement
From: Tatsuo Ishii <ishii@postgresql.org>
X-Mailer: Mew version 6.8 on Emacs 29.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:6cdc:6925:b924:ca8c (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/20251214.220231.820411055090373414.ishii%40postgresql.org>
Precedence: bulk

Currently pgpool does not emit logs for a "sync" message when
log_per_node_statement/notice_per_node_statement enabled. Although
"sync" is not a query statement, I think a sync message plays
important role in extended query protocol since it indicates the
completion of series of extended query protocol messages, and logging
a sync message is important in a trouble shooting (I myself often
enable debug message just to know whether a sync message is sent to
backend or not, but enabling debug message creates lots of noise). So
I propose to add logging for a sync message for upcoming Pgpool-II
4.8.

Comments or suggestions are welcome.
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp