| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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-02-09 13:01:37 |
| Message-ID: | 623F2E6B-AC09-4DF9-B5F4-139DF19A5667@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Feb 9, 2026, at 20:50, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2026-02-09 13:03:16 | Re: log_min_messages per backend type |
| Previous Message | Alvaro Herrera | 2026-02-09 12:58:35 | Re: log_min_messages per backend type |