public inbox for [email protected]  
help / color / mirror / Atom feed
From: Fujii Masao <[email protected]>
To: Jim Jones <[email protected]>
Cc: Maxym Kharchenko <[email protected]>
Cc: Kirill Reshke <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Fujii Masao <[email protected]>
Cc: Kirill Gavrilov <[email protected]>
Cc: Andrey M. Borodin <[email protected]>
Cc: Euler Taveira <[email protected]>
Cc: [email protected]
Subject: Re: Truncate logs by max_log_size
Date: Sat, 4 Jul 2026 00:06:44 +0900
Message-ID: <CAHGQGwHs_zNEajjNX4YJgM8aXsRiYnhM-p4ACw19J-Hftxsw1w@mail.gmail.com> (raw)
In-Reply-To: <CAHGQGwFiQKwvLVG+U0WWNo2kgkQ88FVGhYH_MBZu9Y0SJ8BjDw@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<CALdSSPh6i4mDZ7TLy7dibSfmDQkzFt5NTqv_QrnhPOFEm2xseg@mail.gmail.com>
	<[email protected]>
	<CAHGQGwGEd=PpVWDd05bYM8F6mnxcSNmWL2Ei8JCf5azZSJnYJA@mail.gmail.com>
	<[email protected]>
	<CAHGQGwEc5Dn5KFU04sDp0Kyai2Te5yTuni3QW7pc2a3=343tJQ@mail.gmail.com>
	<[email protected]>
	<CAHGQGwGVxV1YbtLCT+q1yHejBKjLz7L+8r3WJMW=72SDJFW27g@mail.gmail.com>
	<CACsxBjB5+HLw6jJ17qR5vSg+kBb2G5ACSbd_ytZ0HvvD22JqkQ@mail.gmail.com>
	<CAHGQGwFYxCVmL4Bvm61bUW+WUi+YXFHzXo9hFEoSgYT1=fU-+w@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAHGQGwHJHCi=4zEyMc4GJWPC9-oQZHj+9kncxS2442V9PXGgoQ@mail.gmail.com>
	<[email protected]>
	<CAHGQGwFOV+7nOdfoO=kfVH=-fRA9aQE1YcHHLYty3nfQ9rQ4RA@mail.gmail.com>
	<CAHGQGwFiQKwvLVG+U0WWNo2kgkQ88FVGhYH_MBZu9Y0SJ8BjDw@mail.gmail.com>

On Fri, Jul 3, 2026 at 1:24 PM Fujii Masao <[email protected]> wrote:
>
> 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.

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

Regards,

-- 
Fujii Masao





view thread (15+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Truncate logs by max_log_size
  In-Reply-To: <CAHGQGwHs_zNEajjNX4YJgM8aXsRiYnhM-p4ACw19J-Hftxsw1w@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox