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_mbzu9y0sj8b...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/9bfbf5bf61901b57d86fab20559b7973b5a83298 Modified Files -------------- src/test/modules/test_misc/t/014_log_statement_max_length.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
