Horton
Menu

Re: Truncate logs by max_log_size

Jim Jones <jim.jones@uni-muenster.de>

View thread
From: Jim Jones <jim.jones@uni-muenster.de>
To: Fujii Masao <masao.fujii@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, 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-05T09:08:22Z
Lists: pgsql-hackers 

On 05/02/2026 03:17, Fujii Masao wrote:
> At least I'm not for now. So please feel free to work on the patch if
> you'd like!

If nobody is planning to work on this, I can take a look at it next week.

Best, Jim

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.