Re: Truncate logs by max_log_size

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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-03-20 17:33:21
Message-ID: CALdSSPh6i4mDZ7TLy7dibSfmDQkzFt5NTqv_QrnhPOFEm2xseg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 20 Mar 2026 at 16:09, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
>
> rebase
>
> Jim

Hi!
We discussed this patch off-list with Andrey @x4mmm in sight of
CVE-2026-2006. Looks like this patch is not vulnerable, and its use of
pg_mbcliplen are correct.
But I anyway raise this question in lists just for record.

--
Best regards,
Kirill Reshke

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-03-20 17:46:46 Re: Custom oauth validator options
Previous Message Andrey Borodin 2026-03-20 17:05:53 Re: Bug in MultiXact replay compat logic for older minor version after crash-recovery