Re: Progress indication prototype
От | Robert Haas |
---|---|
Тема | Re: Progress indication prototype |
Дата | |
Msg-id | AANLkTinLTUkHaRtWR1V0KC9d+mnV5iMukG52iOTDMoQ5@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Progress indication prototype (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: Progress indication prototype
|
Список | pgsql-hackers |
On Thu, Sep 16, 2010 at 2:52 PM, Peter Eisentraut <peter_e@gmx.net> wrote: >> > a very simple query. >> SELECT * FROM tbl; >> can report reasonable progress, but >> SELECT count(*) FROM tbl; >> cannot, because planned_tuple_count of the aggregation is 1. >> I hope better solutions for the grouping case because they are used >> in complex queries, where the progress counter is eagerly wanted. > > I think that's a problem for a later day. Once we have the interfaces > to report the progress, someone (else) can investigate how to track > progress of arbitrary queries. I reiterate my earlier criticism of this whole approach: it seems to assume that computing query progress is something inexpensive enough that we can afford to do it regardless of whether anyone is looking. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise Postgres Company
В списке pgsql-hackers по дате отправления: