Re: Truncate logs by max_log_size

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Maxym Kharchenko <maxymkharchenko(at)gmail(dot)com>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kirill Gavrilov <diphantxm(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-05-15 10:48:52
Message-ID: 67fcc68a-fce0-42b8-863f-8db5509d1790@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

rebase due to recent changes in src/test/modules/test_misc/meson.build

Jim

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-05-15 10:55:37 Re: (SQL/PGQ) cache lookup failed for label
Previous Message Ayush Tiwari 2026-05-15 10:37:52 Re: (SQL/PGQ) cache lookup failed for label