Horton
Menu

Re: log_min_messages per backend type

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread
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
Date: 2026-02-09T12:50:03Z
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)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Cleanup for log_min_messages changes in 38e0190ced71

  2. Allow log_min_messages to be set per process type

  3. Assign "backend" type earlier during process start-up

  4. Use integer backend type when exec'ing a postmaster child

  5. Sort guc_parameters.dat alphabetically by name

  6. Create a separate file listing backend types

  7. Replace postmaster.c's own backend type codes with BackendType