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@lelarge.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@postgresql.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