From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
Subject: | Re: Bug in the graphical explain |
Date: | 2013-07-18 20:28:11 |
Message-ID: | CA+OCxoxpKUEn+W0pPv-Nfv5rb=0ex+ES439vKbmTbBvGz_KajQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Ashesh; do we have any capacity in the team to spend a little time on
this at the moment? It'll affect the PEM SQL Profiler as well of
course...
On Thu, Jul 18, 2013 at 9:26 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Hi,
>
> I have no idea on how to fix this. I've attached the test case to
> reproduce it.
>
> First execute the test SQL file, then select the last UPDATE query, and
> hit F7. The graphical explain is kinda ugly because two nodes are one on
> the other. That's not the first time I meet this bug. For example, when
> you explain an DELETE query on a table with foreign keys.
>
> If you know how to fix this, that would be great because I'm completely
> lost here.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Neel Patel | 2013-07-19 06:21:29 | Re: Materialized View Patch File |
Previous Message | Guillaume Lelarge | 2013-07-18 20:26:17 | Bug in the graphical explain |