Re: log_min_messages per backend type

> 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
withthe same behavior as before. 

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