Re: Allow cluster_name in log_line_prefix

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow cluster_name in log_line_prefix
Date: 2019-11-10 09:51:17
Message-ID: CAMsr+YGkdtaKow_LedAcdDM=oB09KM6qE9A3VO-LVtym9rbkGA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 3 Nov 2019 at 07:22, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>
wrote:

> On 31/10/2019 08:47, Fujii Masao wrote:
> > On Mon, Oct 28, 2019 at 1:33 PM Craig Ringer <craig(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2019-11-10 09:54:51 Re: [bug fix] Produce a crash dump before main() on Windows
Previous Message Craig Ringer 2019-11-10 09:49:26 Re: [HACKERS] [PATCH] pageinspect function to decode infomasks