Feedback-ID: ia2694551:Fastmail
Date: Mon, 9 Feb 2026 13:50:03 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Euler Taveira <euler@eulerto.com>, japin <japinli@hotmail.com>,
	Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org
Subject: Re: log_min_messages per backend type
Message-ID: <202602091248.6svurucevci2@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <827C26CA-D7C2-4AD9-AEC3-E1E76519453E@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202602091248.6svurucevci2%40alvherre.pgsql>
Precedence: bulk

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)