Request a Demo
Home   >   mailing lists

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 CAHGQGwHs_zNEajjNX4YJgM8aXsRiYnhM-p4ACw19J-Hftxsw1w@mail.gmail.com
Whole thread
In response to Re: Truncate logs by max_log_size  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Tree view 
On Fri, Jul 3, 2026 at 1:24 PM Fujii Masao <masao.fujii@gmail.com> wrote:
>
> 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.

I've pushed the patch, and confirmed that prion is green again.

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Can we get rid of TerminateThread() in pg_dump?
Next
From: "Jonathan Gonzalez V."
Date:
Subject: Re: Path Traversal Vulnerability in pg_dump Directory Format