Re: Progress bar updates

Поиск
Список
Период
Сортировка
От Agent M
Тема Re: Progress bar updates
Дата
Msg-id cb879cca7100128b61864d6b1a06df7a@themactionfaction.com
обсуждение исходный текст
Ответ на Progress bar updates  (Gregory Stark <gsstark@mit.edu>)
Список 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@themactionfaction.com
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: pg_regress breaks on msys
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: pg_regress breaks on msys