From: | Sailesh Krishnamurthy <sailesh(at)cs(dot)berkeley(dot)edu> |
---|---|
To: | pgsql(at)mohawksoft(dot)com |
Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Extended customizing, SQL functions, |
Date: | 2004-06-02 21:08:23 |
Message-ID: | mjq1xkxllbs.fsf@cs.berkeley.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "pgsql" == pgsql <pgsql(at)mohawksoft(dot)com> writes:
pgsql> The have a database of information that is coming in at a
pgsql> high speed regular basis. One bit of information is a
pgsql> value. To get this value they must perform SELECT
pgsql> sum(field) FROM table. Well, this simply does not
pgsql> scale. They've used a trigger system with a small summary
pgsql> table where they update, the number in the sumary
pgsql> field. That works fine, except, that after a few thousand
pgsql> updates, the SELECT time takes a while. Then they have to
pgsql> vacuum constanty. It just seems like an ugly and wastefull
pgsql> process.
Sounds like something that TelegraphCQ can do well ..
http://telegraph.cs.berkeley.edu
--
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan Gardner | 2004-06-02 21:09:17 | Re: process num. |
Previous Message | ivan | 2004-06-02 21:01:11 | process num. |