Subject: Re: backend type in log_line_prefix?
To: Julien Rouhaud <rjuju123@gmail.com>,
 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <c65e5196-4f04-4ead-9353-6088c19615a3@2ndquadrant.com>
 <20200213091428.GA15600@nol>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
Message-ID: <d7dd4aad-c0f3-ecc3-e0f9-def491951e2f@oss.nttdata.com>
Date: Thu, 13 Feb 2020 18:43:32 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0)
 Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <20200213091428.GA15600@nol>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2020/02/13 18:14, Julien Rouhaud wrote:
> On Thu, Feb 13, 2020 at 09:56:38AM +0100, Peter Eisentraut wrote:
>> Attached is a demo patch that adds a placeholder %b for log_line_prefix (not
>> in the default setting) that contains the backend type, the same that you
>> see in pg_stat_activity and in the ps status.  I would have found this
>> occasionally useful when analyzing logs, especially if you have a lot of
>> background workers active.  Thoughts?

If we do this, backend type should be also included in csvlog?

Regarding the patch, postgresql.conf.sample needs to be updated.

Regards,

-- 
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters