| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: expose parallel leader in CSV and log_line_prefix |
| Date: | 2020-07-23 01:42:36 |
| Message-ID: | 20200723014236.GE26630@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2020-07-23 02:54:26 | Re: Default setting for enable_hashagg_disk |
| Previous Message | Tom Lane | 2020-07-23 00:59:04 | Re: expose parallel leader in CSV and log_line_prefix |