Re: Progress bar updates

Dave Page <dpage@vale-housing.co.uk>

From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Gregory Stark" <gsstark@mit.edu>, <pgsql-hackers@postgresql.org>
Date: 2006-07-18T20:08:49Z
Lists: pgsql-hackers
 

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org 
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Gregory Stark
> Sent: 18 July 2006 19:36
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Progress bar updates
> 
> 
> For a first cut this "data structure" could just be a float 
> between 0 and 1.
> Or perhaps it should be two integers, a "current" and an 
> "estimated final".
> That would let the client do more intelligent things when the 
> estimates change
> for the length of the whole job.

Hi Greg,

I would vote for the latter so that we could give more meaningful
feedback - for example, when vacuuming you might give a scale of 0 to
<num tables>. In cases such as COPY where you mightn't have any idea of
an upper bound, then a simple heartbeat could be supplied so at least
the client could count rows (or 100's of rows) processed or whatever.

It would certainly allow us to present a nicer user experience in
pgAdmin :-)

Regards, Dave.