Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: log_min_messages per backend type
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: <202602091248.6svurucevci2@alvherre.pgsql>
Date: Mon, 9 Feb 2026 21:01:37 +0800
Cc: Euler Taveira <euler@eulerto.com>,
 japin <japinli@hotmail.com>,
 Andres Freund <andres@anarazel.de>,
 pgsql-hackers@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <623F2E6B-AC09-4DF9-B5F4-139DF19A5667@gmail.com>
References: <202602091248.6svurucevci2@alvherre.pgsql>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Archived-At: 
 <https://www.postgresql.org/message-id/623F2E6B-AC09-4DF9-B5F4-139DF19A5667%40gmail.com>
Precedence: bulk


> On Feb 9, 2026, at 20:50, Alvaro Herrera <alvherre@alvh.no-ip.org> =
wrote:
>=20
> On 2026-Feb-09, Chao Li wrote:
>=20
>> There=E2=80=99s also a related regression in the interactive case. =
Before this
>> patch, when debugging via psql, a superuser could easily do:
>>=20
>> ```
>> # set log_min_messages =3D debug5
>> ```
>>=20
>> 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.
>=20
> Nonsense.  You can still do the above, and it has the same behavior as
> before.
>=20

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/