Re: Truncate logs by max_log_size

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kirill Gavrilov <diphantxm(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Euler Taveira <euler(at)eulerto(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Truncate logs by max_log_size
Date: 2026-03-20 11:08:59
Message-ID: 061c739f-1ebd-41e8-b49e-8159908f644c@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

rebase

Jim

Attachment Content-Type Size
v8-0001-Add-log_statement_max_length-GUC-to-limit-logged-.patch text/x-patch 10.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2026-03-20 11:28:04 Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication
Previous Message shveta malik 2026-03-20 11:08:12 Re: synchronized_standby_slots behavior inconsistent with quorum-based synchronous replication