I tried sending this with the screenshot attached but it did not seem to
go through, so I am sending again without. The screenshot can be found at
---------- Forwarded message ----------
Date: Wed, 28 Mar 2007 23:16:48 -0700 (PDT)
From: Jeremy Drake <pgsql(at)jdrake(dot)com>
Subject: odd explain diagram in head versions
First off, let me apologize if I am sending this to the wrong list. I
figure, since I am running svn head of pgAdmin against cvs head of
PostgreSQL, rough edges are to be expected, and it would do more good to
make sure the hackers are aware of them than to send some bug report.
I have been enjoying the explain graph functionality of pgadmin for a
couple weeks now, and wishing that I had known about it a couple years
ago. I think it is really great, and would like to thank the authors of
I have a CVS head postgres server, and a database which has foreign key
constraints with ON DELETE CASCADE. I wrote a delete query against the
referred-to table, and hit the explain function in pgadmin. The attached
screenshot was the result.
The data output for this looked like:
"Index Scan using programme_prog_times_idx on programme (cost=0.00..3310.40 rows=2121 width=6) (actual time=15.739..25.609 rows=2353 loops=1)"
" Index Cond: (prog_start >= '2007-04-09 16:45:00-07'::timestamp with time zone)"
"Trigger for constraint credits_prog_id_fkey: time=161.238 calls=2353"
"Trigger for constraint programme_descs_prog_id_fkey: time=154.521 calls=2353"
"Trigger for constraint programme_ratings_prog_id_fkey: time=119.386 calls=2353"
"Total runtime: 484.351 ms"
The problem seems to be that the trigger information is overlaid on the
index scan in the graph, resulting in an unreadable mess of text.
Predestination was doomed from the start.
pgadmin-hackers by date
|Next:||From: Dave Page||Date: 2007-03-29 07:45:20|
|Subject: Re: odd explain diagram in head versions|
|Previous:||From: svn||Date: 2007-03-29 03:25:49|
|Subject: SVN Commit by hiroshi: r6134 - in trunk/pgadmin3/debugger: . include|