From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: expose parallel leader in CSV and log_line_prefix
Date: Wed, 22 Jul 2020 20:59:04 -0400
Message-ID: <90146.1595465944@sss.pgh.pa.us> (raw)
In-Reply-To: <20200723005214.GD26630@paquier.xyz>
References: <20200721043325.GC17300@paquier.xyz>
<20200722153605.GA961@alvherre.pgsql>
<20200723005214.GD26630@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Jul 22, 2020 at 11:36:05AM -0400, Alvaro Herrera wrote:
>> How about we combine both. "Process ID of the parallel group leader, if
>> this process is a parallel query worker. NULL if this process is a
>> parallel group leader or does not participate in parallel query".
> Sounds fine to me. Thanks.
> Do others have any objections with this wording?
Is "NULL" really le mot juste here? If we're talking about text strings,
as the thread title implies (I've not read the patch), then I think you
should say "empty string", because the SQL concept of null doesn't apply.
regards, tom lane
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: tgl@sss.pgh.pa.us, michael@paquier.xyz, alvherre@2ndquadrant.com, pryzby@telsasoft.com, rjuju123@gmail.com, tomas.vondra@2ndquadrant.com
Subject: Re: expose parallel leader in CSV and log_line_prefix
In-Reply-To: <90146.1595465944@sss.pgh.pa.us>
* 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