Re: Progress bar updates - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Progress bar updates
Date
Msg-id 25817.1153319630@sss.pgh.pa.us
Whole thread Raw
In response to Re: Progress bar updates  (Greg Stark <gsstark@mit.edu>)
Responses Re: Progress bar updates
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> In practice, if a query is taking long enough for this feature to be
>> interesting, making another connection and looking to see what's happening
>> is not a problem, and it's likely to be the most practical way anyway for
>> many clients.

> It would be the most practical way for a DBA to monitor an application. But
> it's not going to be convenient for clients like pgadmin or psql.

[ shrug... ]  Let me explain it to you this way: a progress counter
visible through pg_stat_activity is something that might possibly get
done in time for 8.2.  If you insist on having the other stuff right
off the bat as well, it won't get done this cycle.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgxs problem
Next
From: Tom Lane
Date:
Subject: Re: AUTOCOMMIT currently doesn't handle non-transactional commands very well