Thread: [Fwd: request: default width of EXPLAIN ANALYZE output]

Some time ago I sent the request below to pgadmin-hackers, but never saw a reply.  I post here in
case that was on the wrong list.  (I didn't recognize any of the todo items)

I like pgadmin, and I use especially the Query Tool often.

In the Query Tool, the automatic resizing of column width forces one to resize the data grid each
time an explain is run.  (because de width gets set to the lenght of teh string "QUERY PLAN",
which is the name of the 'column').

It would be good to special-case analyze output, and make that one-column output grid of explain
[analyze] as wide as the current window.



Thanks,

Erik Rijkers



---------------------------------------- Original Message ----------------------------------------
Subject: request: default width of EXPLAIN ANALYZE output
From:    "Erik Rijkers" <er@xs4all.nl>
Date:    Tue, January 19, 2010 23:31
To:      pgadmin-hackers@postgresql.org
--------------------------------------------------------------------------------------------------

Hi,

Would it be possible to widen the column width for EXPLAIN [ANALYZE] output to (nearly) window
width  (or at least to more than the narrow default width it has now)?

thanks

Erik Rijkers

Le 28/10/2010 09:53, Erik Rijkers a écrit :
> Some time ago I sent the request below to pgadmin-hackers, but never saw a reply.  I post here in
> case that was on the wrong list.  (I didn't recognize any of the todo items)
> 
> I like pgadmin, and I use especially the Query Tool often.
> 
> In the Query Tool, the automatic resizing of column width forces one to resize the data grid each
> time an explain is run.  (because de width gets set to the lenght of teh string "QUERY PLAN",
> which is the name of the 'column').
> 
> It would be good to special-case analyze output, and make that one-column output grid of explain
> [analyze] as wide as the current window.
> 

I created a ticket for this, so that we can work on this
(http://code.pgadmin.org/trac/ticket/272). But, frankly, I'm not sure I
want to add a special case for this.


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com