database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00
Code Activity

Fix log_statement_max_length test with verbose logs

Browse Source 
Buildfarm member prion reported a failure in the test added by commit
c8bd8387c2 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
This commit is contained in:
Fujii Masao
2026-07-03 14:41:44 +09:00
parent 6d4ca6de97
commit 9bfbf5bf61
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/test/modules/test_misc/t/014_log_statement_max_length.pl
View File

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