Re: expose parallel leader in CSV and log_line_prefix

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: expose parallel leader in CSV and log_line_prefix
Date: 2020-07-17 02:55:45
Message-ID: 20200717025545.GA30699@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2020-07-17 03:04:25 RE: Implement UNLOGGED clause for COPY FROM
Previous Message Thomas Munro 2020-07-17 02:42:18 Re: [PATCH] Add support for choosing huge page size