Re: expose parallel leader in CSV and log_line_prefix

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

> On Fri, Jul 17, 2020 at 7:01 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > Hmm. Knowing if a leader is actually running parallel query or not
> > requires a lookup at lockGroupMembers, that itself requires a LWLock.
> > I think that it would be better to not require that. So what if
> > instead we logged %P only if Myproc has lockGroupLeader set and it
> > does *not* match MyProcPid?

That's what I said first, so +1 for that approach.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2020-07-17 15:44:19 Re: Partitioning and postgres_fdw optimisations for multi-tenancy
Previous Message Dave Cramer 2020-07-17 15:28:50 Re: Patch for reorderbuffer.c documentation.