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: Euler Taveira <euler@eulerto.com>
Cc: japin <japinli@hotmail.com>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org, Chao Li <li.evan.chao@gmail.com>
Date: 2026-01-21T14:51:40Z
Lists: pgsql-hackers 
On 2026-Jan-15, Euler Taveira wrote:

> @@ -586,6 +588,8 @@ SubPostmasterMain(int argc, char *argv[])
>  	IsPostmasterEnvironment = true;
>  	whereToSendOutput = DestNone;
>  
> +	MyBackendType = B_BACKEND;
> +
>  	/*
>  	 * Capture the end of process creation for logging. We don't include the
>  	 * time spent copying data from shared memory and setting up the backend.

BTW I think SubPostmasterMain() shouldn't do this.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  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