Re: expose parallel leader in CSV and log_line_prefix
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Julien Rouhaud <rjuju123@gmail.com>, pgsql-hackers@postgresql.org
Date: 2020-07-17T02:55:45Z
Lists: pgsql-hackers
On 2020-Jul-17, Michael Paquier wrote: > Please note that this choice comes from BecomeLockGroupLeader(), where > a leader registers itself in lockGroupLeader, and remains set as such > as long as the process is alive so we would always get a value for a > process once it got involved in parallel query. This patch is just Oh, ugh, I don't like that part much. If you run connections through a connection pooler, it's going to be everywhere. Let's put it there only if the connection *is* running a parallel query, without being too stressed about the startup and teardown sequence. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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