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 23:14:19 |
Message-ID: | AANLkTi=TcuMA38oGUKX9p5WVPpY+M3L0XUp7=PLT+LCT@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 16, 2010 at 4:57 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On tor, 2010-09-16 at 15:56 -0400, Robert Haas wrote:
>> 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.
>
> That assumption appears to hold so far.
It seems unlikely to hold in the general case, though, particularly if
you want to do it to be accurate. The problems with database-wide
VACUUM seem likely to be the tip of the iceberg.
> Anyway, do you have an alternative suggestion?
I think that there should be a function which returns just this one
piece of data and is not automatically called as part of select * from
pg_stat_activity. Then we could eventually decide to give backends a
way to know if that function had been invoked on them and how
recently.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-09-16 23:45:00 | Re: Server crash during simple c-language function |
Previous Message | Kevin Grittner | 2010-09-16 23:09:45 | Re: Serializable Snapshot Isolation |