On Fri, Jul 3, 2026 at 9:56 AM Fujii Masao <[email protected]> wrote: > Thanks for the review! I've pushed the patch.
The buildfarm member prion reported the failure [1]. It looks like the failure occurs because prion runs with log_error_verbosity = verbose, which inserts the SQLSTATE between "LOG:" and the message text. The log_statement_max_length = 0 test expected "statement:" to appear immediately after "LOG:", so it failed even though the server correctly logged an empty statement body. The attached patch fixes the test. Regards, [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2026-07-03%2002%3A23%3A06 -- Fujii Masao
v1-0001-Fix-log_statement_max_length-test-with-verbose-lo.patch
Description: Binary data
