| From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
|---|---|
| To: | 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 08:51:33 |
| Message-ID: | 1153385492.5683.183.camel@coppola.muc.ecircle.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | moises | 2006-07-20 08:57:16 | Real Time Data Base using Postgre |
| Previous Message | Adrian Maier | 2006-07-20 08:13:48 | Re: float8 regression failure (HEAD, cygwin) |