Re: expose parallel leader in CSV and log_line_prefix
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Justin Pryzby <pryzby@telsasoft.com>, Julien Rouhaud <rjuju123@gmail.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, pgsql-hackers@postgresql.org
Date: 2020-07-23T01:42:36Z
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
Commits
-
Add %P to log_line_prefix for parallel group leader
- b8fdee7d0ca8 14.0 landed
-
Tweak behavior of pg_stat_activity.leader_pid
- 21b0055359f0 13.0 landed
- 11a68e4b53ff 14.0 landed
-
Add leader_pid to pg_stat_activity
- b025f32e0b5d 13.0 cited