Re: log_min_messages per backend type

From: "Euler Taveira" <euler(at)eulerto(dot)com>
To: japin <japinli(at)hotmail(dot)com>, "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: "Andres Freund" <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: log_min_messages per backend type
Date: 2025-11-06 13:09:06
Message-ID: 72e809ff-c842-4f98-93f1-26a3cb3d92d0@app.fastmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Oct 5, 2025, at 11:18 AM, Euler Taveira wrote:
> This new patch contains the following changes:
>
> - patch was rebased
> - use commit dbf8cfb4f02
> - use some GUC memory allocation functions
> - avoid one memory allocation (suggested by Japin Li)
> - rename backend type: logger -> syslogger
> - adjust tests to increase test coverage
> - improve documentation and comments to reflect the current state
>

Patch was rebased since commit fce7c73fba4 broke it. No modifications.

--
Euler Taveira
EDB https://www.enterprisedb.com/

Attachment Content-Type Size
v5-0001-log_min_messages-per-backend-type.patch text/x-patch 25.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-11-06 13:17:46 Re: COPY WHERE clause generated/system column reference
Previous Message Ashutosh Bapat 2025-11-06 12:59:00 Re: Calling PGReserveSemaphores() from CreateOrAttachShmemStructs