| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | Maxym Kharchenko <maxymkharchenko(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kirill Gavrilov <diphantxm(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Truncate logs by max_log_size |
| Date: | 2026-07-03 15:06:44 |
| Message-ID: | CAHGQGwHs_zNEajjNX4YJgM8aXsRiYnhM-p4ACw19J-Hftxsw1w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 3, 2026 at 1:24 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Fri, Jul 3, 2026 at 9:56 AM Fujii Masao <masao(dot)fujii(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Gonzalez V. | 2026-07-03 15:07:17 | Re: Path Traversal Vulnerability in pg_dump Directory Format |
| Previous Message | Heikki Linnakangas | 2026-07-03 15:05:14 | Re: Can we get rid of TerminateThread() in pg_dump? |