Re: Truncate logs by max_log_size

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Cc: Euler Taveira <euler(at)eulerto(dot)com>, diPhantxm <diphantxm(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Truncate logs by max_log_size
Date: 2024-10-01 12:43:20
Message-ID: CAKAnmmKq+L1JrdfNOT6x5pebVj+Ezor==L5w6BW_KWYoMB7U7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 27, 2024 at 6:37 AM Andrey M. Borodin <x4mmm(at)yandex-team(dot)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?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-10-01 12:43:33 Re: Conflict detection for update_deleted in logical replication
Previous Message Michał Kłeczek 2024-10-01 12:30:04 Re: SET or STRICT modifiers on function affect planner row estimates