Re: Truncate logs by max_log_size

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Euler Taveira <euler(at)eulerto(dot)com>
Cc: diPhantxm <diphantxm(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Truncate logs by max_log_size
Date: 2024-09-27 10:36:58
Message-ID: 4DA5A159-39FD-47DB-95E5-A4F65BC5782A@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 Sep 2024, at 03:30, Euler Taveira <euler(at)eulerto(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dagfinn Ilmari Mannsåker 2024-09-27 10:44:25 Re: Add has_large_object_privilege function
Previous Message Florents Tselai 2024-09-27 10:28:21 Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part