On 2020-Mar-31, Tom Lane wrote:
> Alvaro Herrera writes:
> > We have not fixed this, have we?
>
> Isn't this 10013684970453a0ddc86050bba813c64321 ?
Ah, right, another thread reporting the same thing, two months after
this one.
Thanks both :-)
--
Álvaro Herrerahttps://www.
Alvaro Herrera writes:
> We have not fixed this, have we?
Isn't this 10013684970453a0ddc86050bba813c64321 ?
regards, tom lane
On 2020-03-31 14:06:50 -0300, Alvaro Herrera wrote:
> We have not fixed this, have we?
I thought we did:
commit 10013684970453a0ddc86050bba813c64321
Author: Tom Lane
Date: 2020-01-25 18:16:42 -0500
Clean up EXPLAIN's handling of per-worker details.
Previously, it was possible for
We have not fixed this, have we?
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Hi hackers,
On Fri, 23 Aug 2019 09:30:59 -0400
Andrew Dunstan wrote:
> On 8/23/19 8:47 AM, Pierre Giraud wrote:
> > "Plans": [
> > {
> > "Node Type": "Sort",
> > "Parent Relationship": "Outer",
> > "Parallel Aware": false,
> > "Actual Startup
On 8/23/19 8:47 AM, Pierre Giraud wrote:
> "Plans": [
> {
> "Node Type": "Sort",
> "Parent Relationship": "Outer",
> "Parallel Aware": false,
> "Actual Startup Time": 1558.638,
> "Actual Total Time": 2127.522,
> "Actual Row
Hi,
I'm currently working on a tool to visualize an execution plan [1]. For
those who know PEV, it's actually a fork of this great tool since it
hasn't been active for more than 2 years.
Among other things, I'd like to show information for the parallel
queries. First of which is information about
