| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 00:59:04 |
| Message-ID: | 90146.1595465944@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-07-23 01:42:36 | Re: expose parallel leader in CSV and log_line_prefix |
| Previous Message | Michael Paquier | 2020-07-23 00:52:14 | Re: expose parallel leader in CSV and log_line_prefix |