From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: expose parallel leader in CSV and log_line_prefix
Date: Fri, 10 Jul 2020 13:16:40 -0400
Message-ID: <20200710171640.GA26222@alvherre.pgsql> (raw)
In-Reply-To: <20200710165524.GL26220@telsasoft.com>
On 2020-Jul-10, Justin Pryzby wrote:
> On Fri, Jul 10, 2020 at 12:45:29PM -0400, Alvaro Herrera wrote:
> > I think it's overly verbose; all non-parallel backends are going to get
> > their own PID twice, and I'm not sure this is going to be great to
> > parse. I think it would be more sensible that if the process does not
> > have a parent (leader), %P expands to empty.
>
> That's what's done.
>
> + <entry>Process ID of the parallel group leader if this process was
> + at some point involved in parallel query, otherwise null. For a
> + parallel group leader itself, this field is set to its own process
> + ID.</entry>
Oh, okay by me then.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, pryzby@telsasoft.com, rjuju123@gmail.com
Subject: Re: expose parallel leader in CSV and log_line_prefix
In-Reply-To: <20200710171640.GA26222@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox