From: | "Luke Lonergan" <LLonergan(at)greenplum(dot)com> |
---|---|
To: | "Csaba Nagy" <nagy(at)ecircle-ag(dot)com>, "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com> |
Cc: | "postgres hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Progress bar updates |
Date: | 2006-07-20 15:36:55 |
Message-ID: | 3E37B936B592014B978C4415F90D662D01F73A91@MI8NYCMAIL06.Mi8.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 (www.good.com)
-----Original Message-----
From: Csaba Nagy [mailto:nagy(at)ecircle-ag(dot)com]
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.
Cheers,
Csaba.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2006-07-20 15:51:27 | Re: Units in postgresql.conf |
Previous Message | Hiroshi Saito | 2006-07-20 15:24:01 | Re: pg_regress breaks on msys |