On Wednesday 19 July 2006 07:33, Tom Lane wrote:
Greg Stark <gsst...@mit.edu> writes:
Tom Lane <tg...@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.
Having the progress, or estimated time of completion in pg_stat_activity
sounds like a good starting point, the rest of the desired features can be
bolted on top of this down the road
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
18 messages in org.postgresql.pgsql-hackersRe: Progress bar updates
