Horton
Menu

Re: Truncate logs by max_log_size

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Jim Jones <jim.jones@uni-muenster.de>, Kirill Gavrilov <diphantxm@gmail.com>, Kirill Reshke <reshkekirill@gmail.com>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Euler Taveira <euler@eulerto.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-02-05T02:17:45Z
Lists: pgsql-hackers 
On Wed, Feb 4, 2026 at 6:48 PM Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> On 2025-Apr-01, Fujii Masao wrote:
>
> > Since this patch is marked as ready-for-committer, I started reviewing it.
> > Basically I like the proposed idea.
>
> Hello, is this something that anybody is working on?
> https://commitfest.postgresql.org/patch/5272/

At least I'm not for now. So please feel free to work on the patch if
you'd like!

Regards,

-- 
Fujii Masao

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix log_statement_max_length test with verbose logs

  2. Add log_statement_max_length GUC to limit logged statement text

  3. Improve user control over truncation of logged bind-parameter values.