| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Pierre Giraud <pierre(dot)giraud(at)dalibo(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Explain: Duplicate key "Workers" in JSON format |
| Date: | 2020-03-31 17:16:22 |
| Message-ID: | 20200331171622.gzjsjkphq6wug2sz@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-03-31 14:06:50 -0300, Alvaro Herrera wrote:
> We have not fixed this, have we?
I thought we did:
commit 10013684970453a0ddc86050bba813c611114321
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: 2020-01-25 18:16:42 -0500
Clean up EXPLAIN's handling of per-worker details.
Previously, it was possible for EXPLAIN ANALYZE of a parallel query
to produce several different "Workers" fields for a single plan node,
because different portions of explain.c independently generated
per-worker data and wrapped that output in separate fields. This
is pretty bogus, especially for the structured output formats: even
if it's not technically illegal, most programs would have a hard time
dealing with such data.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2020-03-31 17:16:56 | [PATCH] Fix type var declaration (src/backend/access/brin/brin.c) |
| Previous Message | Alvaro Herrera | 2020-03-31 17:06:50 | Re: Explain: Duplicate key "Workers" in JSON format |