Re: Truncate logs by max_log_size
Jim Jones <jim.jones@uni-muenster.de>
From: Jim Jones <jim.jones@uni-muenster.de>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Fujii Masao <masao.fujii@gmail.com>,
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-03-20T11:08:59Z
Lists: pgsql-hackers
Attachments
- v8-0001-Add-log_statement_max_length-GUC-to-limit-logged-.patch (text/x-patch) patch v8-0001
rebase Jim
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix log_statement_max_length test with verbose logs
- 9bfbf5bf6190 master landed
-
Add log_statement_max_length GUC to limit logged statement text
- c8bd8387c27a master landed
-
Improve user control over truncation of logged bind-parameter values.
- 0b34e7d307e6 13.0 cited