Re: log_min_messages per backend type

Chao Li <li.evan.chao@gmail.com>

From: Chao Li <li.evan.chao@gmail.com>

To: Euler Taveira <euler@eulerto.com>

Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, japin <japinli@hotmail.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org

Date: 2025-12-11T02:11:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow log_min_messages to be set per process type
- 38e0190ced71 19 (unreleased) landed
Assign "backend" type earlier during process start-up
- 0c8e082fba8d 19 (unreleased) landed
Use integer backend type when exec'ing a postmaster child
- f1cd34f95272 19 (unreleased) landed
Sort guc_parameters.dat alphabetically by name
- fce7c73fba4e 19 (unreleased) cited
Create a separate file listing backend types
- dbf8cfb4f02e 19 (unreleased) cited


> On Dec 11, 2025, at 09:57, Euler Taveira <euler@eulerto.com> wrote:
> 
> 
>> In the “if” and “else” clauses, there are duplicate code to valid log 
>> levels. We should refactor the code to avoid the duplication. For 
>> example, pull up “loglevel” to the “for” loop level, then we can valid 
>> it after the “if-else”.
>> 
> 
> The for loop is duplicate but if you create a separate function for it but the
> result is:
> 
> src/backend/commands/variable.c | 43 ++++++++++++++++++++++---------------------
> 1 file changed, 22 insertions(+), 21 deletions(-)
> 
> 

I don’t think we need to add a separate function. We can use ‘if-else” to parse log level, then verify it after “if-else”.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/