This is how netezza and teradata do it and it works very well.

In each of their cases you can see a graphical representation of the plan with 
progress for each stage.

For the command line it would be great to just dump the current status, which 
would provide a snapshot of the explain analyze.

- Luke

Sent from my GoodLink synchronized handheld (

 -----Original Message-----
From:   Csaba Nagy [mailto:[EMAIL PROTECTED]
Sent:   Thursday, July 20, 2006 04:52 AM Eastern Standard Time
To:     Andrew Hammond
Cc:     postgres hackers
Subject:        Re: [HACKERS] Progress bar updates

> We already have EXPLAIN ANALYZE. Perhaps the right way to do this is
> something that provides similar output. I could see something that
> looks like EXPLAIN for the parts that have not yet executed, something
> reasonable to show progress of the currently active part of the plan
> (current time, rows, loops), and EXPLAIN ANALYZE output for the parts
> which have been completed.

Now this is something that would really help testing a system, by
dynamically seeing the plans of queries which run too long. That
combined with the ability to see the values of bind parameters would be
a useful debug aid.


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to