Re: expose parallel leader in CSV and log_line_prefix

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: expose parallel leader in CSV and log_line_prefix
Date: 2020-07-10 02:20:23
Message-ID: 20200710022023.GE26220@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 10, 2020 at 11:09:40AM +0900, Michael Paquier wrote:
> On Thu, Jul 09, 2020 at 01:53:39PM +0200, Julien Rouhaud wrote:
> > Sure! I've been quite busy with internal work duties recently but
> > I'll review this patch shortly. Thanks for the reminder!
>
> Hmm. In which cases would it be useful to have this information in
> the logs knowing that pg_stat_activity lets us know the link between
> both the leader and its workers?

PSA is an instantaneous view whereas the logs are a record. That's important
for shortlived processes (like background workers) or in the case of an ERROR
or later crash.

Right now, the logs fail to include that information, which is deficient. Half
the utility is in showing *that* the log is for a parallel worker, which is
otherwise not apparent.

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2020-07-10 03:16:11 Re: Global snapshots
Previous Message tsunakawa.takay@fujitsu.com 2020-07-10 02:10:20 RE: Postgres is not able to handle more than 4k tables!?