Skip site navigation (1) Skip section navigation (2)

Re: Extended customizing, SQL functions,

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 (view raw or flat)
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



In response to

pgsql-hackers by date

Next:From: Jonathan GardnerDate: 2004-06-02 21:09:17
Subject: Re: process num.
Previous:From: ivanDate: 2004-06-02 21:01:11
Subject: process num.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group