Re: log_min_messages per backend type

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Euler Taveira <euler(at)eulerto(dot)com>, japin <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: log_min_messages per backend type
Date: 2026-07-20 12:15:36
Message-ID: al4PzUn6y82eP-t1@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

Here's a couple of trivial cleanups of this code. 0001 simplifies code
and removes a duplicate by creating a small subroutine; 0002 also
simplifies memory freeing a tad, by freeing allocations as soon as
no longer needed instead of waiting and being forced to duplicate the
frees in several places.

This is two commits here just for ease of review, but I'd probably push
as one commit (and without backpatch).

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"World domination is proceeding according to plan" (Andrew Morton)

Attachment Content-Type Size
0001-simplify-coding-in-check_log_min_messages.patch text/x-diff 3.3 KB
0002-memory-free-simplify.patch text/x-diff 1.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2026-07-20 12:21:15 Re: Making the ENUM operators LEAKPROOF
Previous Message Andrey Borodin 2026-07-20 12:14:27 Re: nbtree backwards scan test coverage