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-02-09 12:50:03
Message-ID: 202602091248.6svurucevci2@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Curiosity is the hope that something wondrous waits just out of sight,
for we are surrounded by a garden of miracles" (Namron)
(Marjorie Liu and Sana Takeda, Monstress: Inferno)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Cédric Villemain 2026-02-09 12:58:00 Re: alter check constraint enforceability
Previous Message Alvaro Herrera 2026-02-09 12:40:51 Re: log_min_messages per backend type