Re: expose parallel leader in CSV and log_line_prefix - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: expose parallel leader in CSV and log_line_prefix
Date
Msg-id 20200710161115.GK26220@telsasoft.com
Whole thread Raw
In response to Re: expose parallel leader in CSV and log_line_prefix  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: expose parallel leader in CSV and log_line_prefix
List pgsql-hackers
On Fri, Jul 10, 2020 at 05:13:26PM +0200, Julien Rouhaud wrote:
> There's a thinko in the padding handling.  It should be dones whether MyProc
> and/or lockGroupLeader is NULL or not, and only if padding was asked, like it's
> done for case 'd' for instance.
> 
> Also, the '%k' escape sounds a bit random.  Is there any reason why we don't
> use any uppercase character for log_line_prefix?  %P could be a better
> alternative, otherwise maybe %g, as GroupLeader/Gather?

Thanks for looking.  %P is a good idea - it's consistent with ps and pkill and
probably other %commands.  I also amended the docs.

-- 
Justin

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GSSENC'ed connection stalls while reconnection attempts.
Next
From: Tom Lane
Date:
Subject: Re: Stale external URL in doc?