From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
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: Thu, 23 Jul 2020 10:42:36 +0900
Message-ID: <20200723014236.GE26630@paquier.xyz> (raw)
In-Reply-To: <90146.1595465944@sss.pgh.pa.us>
References: <20200721043325.GC17300@paquier.xyz>
<20200722153605.GA961@alvherre.pgsql>
<20200723005214.GD26630@paquier.xyz>
<90146.1595465944@sss.pgh.pa.us>
On Wed, Jul 22, 2020 at 08:59:04PM -0400, Tom Lane wrote:
> 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.
Sorry for the confusion. This part of the thread applies to the open
item for v13 related to pg_stat_activity's leader_pid. A different
thread should have been spawned for this specific topic, but things
are as they are..
--
Michael
Attachments:
[application/pgp-signature] signature.asc (832B, ../20200723014236.GE26630@paquier.xyz/2-signature.asc)
download
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: michael@paquier.xyz, tgl@sss.pgh.pa.us, 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: <20200723014236.GE26630@paquier.xyz>
* 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