From: | Agent M <agentm(at)themactionfaction(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Progress bar updates |
Date: | 2006-07-20 02:41:10 |
Message-ID: | cb879cca7100128b61864d6b1a06df7a@themactionfaction.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Why make it so complicated?
There could be a guc to indicate that the client is interested in
progress updates. For the execution phase, elog(INFO,...) could be
emitted for each major plan node. (The client would probably run the
explain plan beforehand or it would be embedded in the elog).
During the downloading of the rows, the client would display the bar
relative to the number of estimated rows returned.
-M
On Jul 18, 2006, at 2:35 PM, Gregory Stark wrote:
>
> Has anyone looked thought about what it would take to get progress
> bars from
> clients like pgadmin? (Or dare I even suggest psql:)
>
> My first thought would be a message like CancelQuery which would cause
> the
> backend to peek into a static data structure and return a message that
> the
> client could parse and display something intelligent. Various commands
> would
> then stuff information into this data structure as they worked.
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
AgentM
agentm(at)themactionfaction(dot)com
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-07-20 02:57:40 | Re: pg_regress breaks on msys |
Previous Message | Tom Lane | 2006-07-20 02:33:28 | Re: pg_regress breaks on msys |