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: Jim Jones <jim.jones@uni-muenster.de>
Cc: Kirill Reshke <reshkekirill@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>, Fujii Masao <masao.fujii@oss.nttdata.com>, Kirill Gavrilov <diphantxm@gmail.com>, "Andrey M. Borodin" <x4mmm@yandex-team.ru>, Euler Taveira <euler@eulerto.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-04-10T02:01:12Z
Lists: pgsql-hackers 
On Fri, Apr 10, 2026 at 7:36 AM Jim Jones <jim.jones@uni-muenster.de> wrote:
> > I see the patch has been moved to CommitFest PG20-1. Once development for v20
> > starts, I'd like to commit it.
>
>
> Terrific. Thanks!

Thanks for updating the patch! LGTM. Let's wait for next CF for v20 to begin.

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.