From: Fujii Masao <fujii@postgresql.org>
Date: Fri, 3 Jul 2026 05:41:44 +0000 (+0900)
Subject: Fix log_statement_max_length test with verbose logs
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9bfbf5bf61901b57d86fab20559b7973b5a83298;p=thirdparty%2Fpostgresql.git

Fix log_statement_max_length test with verbose logs

Buildfarm member prion reported a failure in the test added by commit
c8bd8387c27 to verify that the server logs an empty statement body
when log_statement_max_length = 0.

The test assumed that "statement:" would appear immediately after
"LOG:" in the logged statement message. However, prion runs with
log_error_verbosity = verbose, which inserts the SQLSTATE between
"LOG:" and the message text. As a result, the test failed even though
the server behaved correctly.

Per buildfarm member prion.

Discussion: https://postgr.es/m/CAHGQGwFiQKwvLVG+U0WWNo2kgkQ88FVGhYH_MBZu9Y0SJ8BjDw@mail.gmail.com
---

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).