Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1tq1N7-00Fk81-Lo
	for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Mar 2025 02:54:05 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1tq1N6-00D1cP-ED
	for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Mar 2025 02:54:04 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <masao.fujii@oss.nttdata.com>)
	id 1tq1N6-00D1bs-3x
	for pgsql-hackers@lists.postgresql.org; Thu, 06 Mar 2025 02:54:04 +0000
Received: from oss.nttdata.com ([49.212.34.109])
	by makus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <masao.fujii@oss.nttdata.com>)
	id 1tq1N1-001Dl0-2a
	for pgsql-hackers@lists.postgresql.org;
	Thu, 06 Mar 2025 02:54:01 +0000
Received: from [192.168.11.5] (p1695135-ipoe.ipoe.ocn.ne.jp [118.0.92.134])
	by oss.nttdata.com (Postfix) with ESMTPSA id 53F5061A7D;
	Thu,  6 Mar 2025 11:53:55 +0900 (JST)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.103.11 at oss.nttdata.com
Message-ID: <16c29677-3135-486a-860c-f1efebe4776b@oss.nttdata.com>
Date: Thu, 6 Mar 2025 11:53:54 +0900
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: log_min_messages per backend type
Content-Language: en-US
To: Euler Taveira <euler@eulerto.com>,
 Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers@lists.postgresql.org
References: <202502051851.2nvzh3a6ukzc@alvherre.pgsql>
 <313aa202-b5fa-4e3f-95d0-83425575c66d@app.fastmail.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
In-Reply-To: <313aa202-b5fa-4e3f-95d0-83425575c66d@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: <https://www.postgresql.org/message-id/16c29677-3135-486a-860c-f1efebe4776b%40oss.nttdata.com>
Precedence: bulk



On 2025/03/05 9:33, Euler Taveira wrote:
>> > +        Valid <literal>BACKENDTYPE</literal> values are <literal>ARCHIVER</literal>,
>> > +        <literal>AUTOVACUUM</literal>, <literal>BACKEND</literal>,
>> > +        <literal>BGWORKER</literal>, <literal>BGWRITER</literal>,
>> > +        <literal>CHECKPOINTER</literal>, <literal>LOGGER</literal>,
>> > +        <literal>SLOTSYNCWORKER</literal>, <literal>WALRECEIVER</literal>,
>> > +        <literal>WALSENDER</literal>, <literal>WALSUMMARIZER</literal>, and
>> > +        <literal>WALWRITER</literal>.

What about postmaster?

For parallel workers launched for parallel queries, should they follow
the backend's log level or the background worker's? Since they operate
as part of a parallel query executed by a backend, it seems more logical
for them to follow the backend's setting.

+	[B_CHECKPOINTER] = "checkpointer",
+	[B_STARTUP] = "backend",	/* XXX same as backend? */

I like the idea of allowing log levels to be set per process.
There were times I wanted to use debug5 specifically for
the startup process when troubleshooting WAL replay. It would be
helpful to distinguish the startup process from a regular backend,
so we can set its log level independently.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION