Re: Truncate logs by max_log_size - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Truncate logs by max_log_size
Date
Msg-id CAHGQGwFiQKwvLVG+U0WWNo2kgkQ88FVGhYH_MBZu9Y0SJ8BjDw@mail.gmail.com
Whole thread
In response to Re: Truncate logs by max_log_size  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Truncate logs by max_log_size
List pgsql-hackers
On Fri, Jul 3, 2026 at 9:56 AM Fujii Masao <masao.fujii@gmail.com> 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

Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication
Next
From: Ashutosh Bapat
Date:
Subject: Re: Wrong query result w/ propgraph single lateral col reference