Re: Allow cluster_name in log_line_prefix - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: Allow cluster_name in log_line_prefix
Date
Msg-id CAMsr+YGkdtaKow_LedAcdDM=oB09KM6qE9A3VO-LVtym9rbkGA@mail.gmail.com
Whole thread Raw
In response to Re: Allow cluster_name in log_line_prefix  (Vik Fearing <vik.fearing@2ndquadrant.com>)
List pgsql-hackers
On Sun, 3 Nov 2019 at 07:22, Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
On 31/10/2019 08:47, Fujii Masao wrote:
> On Mon, Oct 28, 2019 at 1:33 PM Craig Ringer <craig@2ndquadrant.com> wrote:
>> Hi folks
>>
>> I was recently surprised to notice that log_line_prefix doesn't support a cluster_name placeholder. I suggest adding one. If I don't hear objections I'll send a patch.
> If we do this, cluster_name should be included in csvlog?


Yes, absolutely.

Ok, I can put that together soon then.

I don't think it's too likely that people will shout about it being added to csvlog. People using csvlog tend to be ingesting and postprocessing their logs anyway. Plus gzip is really, really good at dealing with redundancy.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 2ndQuadrant - PostgreSQL Solutions for the Enterprise

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks
Next
From: Craig Ringer
Date:
Subject: Re: [bug fix] Produce a crash dump before main() on Windows