Re: log_min_messages per backend type

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

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

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: Euler Taveira <euler@eulerto.com>, japin <japinli@hotmail.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org

Date: 2026-02-09T13:01:37Z

Lists: pgsql-hackers


> On Feb 9, 2026, at 20:50, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> 
> On 2026-Feb-09, Chao Li wrote:
> 
>> There’s also a related regression in the interactive case. Before this
>> patch, when debugging via psql, a superuser could easily do:
>> 
>> ```
>> # set log_min_messages = debug5
>> ```
>> 
>> to temporarily increase verbosity for the current backend. With the
>> new syntax, doing the equivalent now requires copying the entire
>> log_min_messages string and modifying just one part, which feels
>> noticeably heavier for quick debugging.
> 
> Nonsense.  You can still do the above, and it has the same behavior as
> before.
> 

Ah, yes, for the SET scenario, it sets the log level for all types, so the backend type gets the value, which ends up with the same behavior as before.

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

Commits

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

Cleanup for log_min_messages changes in 38e0190ced71
- 1efdd7cc630a 19 (unreleased) landed
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
Replace postmaster.c's own backend type codes with BackendType
- 18d67a8d7d30 18.0 cited