From ea14e198cc867ae53a0b535b71bb7afd4f734c56 Mon Sep 17 00:00:00 2001
From: Fujii Masao <fujii@postgresql.org>
Date: Fri, 3 Jul 2026 13:13:00 +0900
Subject: [PATCH v1] Fix log_statement_max_length test with verbose logs

---
 src/test/modules/test_misc/t/014_log_statement_max_length.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/test/modules/test_misc/t/014_log_statement_max_length.pl b/src/test/modules/test_misc/t/014_log_statement_max_length.pl
index 6cd45f2ee83..b1ce6068f5d 100644
--- a/src/test/modules/test_misc/t/014_log_statement_max_length.pl
+++ b/src/test/modules/test_misc/t/014_log_statement_max_length.pl
@@ -62,7 +62,7 @@ $node->psql(
 	'postgres', "
 	SET log_statement_max_length TO 0;
 	SELECT '123456789ABCDEF';");
-ok($node->log_contains(qr/LOG:\s+statement:\s*$/m, $log_offset),
+ok($node->log_contains(qr/statement:\s*$/m, $log_offset),
 	"0 logs an empty statement body");
 
 # Verify truncation via the extended query protocol (execute message).
-- 
2.53.0

