From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: expose parallel leader in CSV and log_line_prefix |
Date: | 2020-07-10 17:16:40 |
Message-ID: | 20200710171640.GA26222@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-07-10 17:24:21 | Re: SQL-standard function body |
Previous Message | Mark Dilger | 2020-07-10 17:13:55 | Re: factorial function/phase out postfix operators? |