Horton
Menu

Re: Truncate logs by max_log_size

Andrey Borodin <x4mmm@yandex-team.ru>

View thread
From: "Andrey M. Borodin" <x4mmm@yandex-team.ru>
To: Euler Taveira <euler@eulerto.com>
Cc: diPhantxm <diphantxm@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-09-27T10:36:58Z
Lists: pgsql-hackers 

> On 27 Sep 2024, at 03:30, Euler Taveira <euler@eulerto.com> wrote:
> 
> Let's say you arbitrarily provide max_log_size = 100

Consider max_log_size = 10Mb. The perspective might look very different. It’s not about WHERE anymore. It's a guard against heavy abuse.

The feature looks very important for me.


Best regards, Andrey Borodin.

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.