Horton
Menu

Re: Truncate logs by max_log_size

Greg Sabino Mullane <htamfids@gmail.com>

View thread
From: Greg Sabino Mullane <htamfids@gmail.com>
To: "Andrey M. Borodin" <x4mmm@yandex-team.ru>
Cc: Euler Taveira <euler@eulerto.com>, diPhantxm <diphantxm@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-10-01T12:43:20Z
Lists: pgsql-hackers 
On Fri, Sep 27, 2024 at 6:37 AM Andrey M. Borodin <x4mmm@yandex-team.ru>
wrote:

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

Can you elaborate on this? Do you mean someone purposefully writing large
entries to your log file?

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.