| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-21 04:38:21 |
| Message-ID: | 20200721043821.GD17300@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 17, 2020 at 07:34:54AM +0200, Julien Rouhaud wrote:
> I had the same concern and was thinking about this approach too.
> Another argument is that IIUC any log emitted due to
> log_min_duration_statement wouldn't see the backend as executing a
> parallel query, since the workers would already have been shut down.
Not sure that it is worth bothering about this case. You could also
have a backend killed by log_min_duration_statement on a query that
did not involve parallel query, where you would still report the PID
if it got involved at least once in parallel query for a query before
that.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amul Sul | 2020-07-21 05:28:11 | Re: new heapcheck contrib module |
| Previous Message | Michael Paquier | 2020-07-21 04:33:25 | Re: expose parallel leader in CSV and log_line_prefix |