Horton
Menu

Re: Truncate logs by max_log_size

Álvaro Herrera <alvherre@kurilemu.de>

View thread
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: 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-04T09:48:23Z
Lists: pgsql-hackers 
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/
Apparently it was very close to done but was abandoned after several
rounds of review at the start of the cycle.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Computing is too important to be left to men." (Karen Spärck Jones)

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.