Re: Progress bar updates - Mailing list pgsql-hackers

From Luke Lonergan
Subject Re: Progress bar updates
Date
Msg-id 3E37B936B592014B978C4415F90D662D01F73A91@MI8NYCMAIL06.Mi8.com
Whole thread Raw
In response to Progress bar updates  (Gregory Stark <gsstark@mit.edu>)
List 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@ecircle-ag.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?
              http://archives.postgresql.org




pgsql-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: pg_regress breaks on msys
Next
From: Tom Lane
Date:
Subject: Re: float8 regression failure (HEAD, cygwin)