From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Progress indication prototype |
Date: | 2010-09-16 19:56:40 |
Message-ID: | AANLkTinLTUkHaRtWR1V0KC9d+mnV5iMukG52iOTDMoQ5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 16, 2010 at 2:52 PM, Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-09-16 20:37:48 | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
Previous Message | Greg Smith | 2010-09-16 19:49:46 | Re: Day 01/31 |