From: | Bricklen Anderson <BAnderson(at)PresiNET(dot)com> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Sam Vilain <sam(at)vilain(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Prefetch |
Date: | 2005-05-11 14:23:20 |
Message-ID: | 42821558.1010707@PresiNET.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Christopher Kings-Lynne wrote:
>> Another trick you can use with large data sets like this when you want
>> results
>> back in seconds is to have regularly updated tables that aggregate the
>> data
>> along each column normally aggregated against the main data set.
>
>
>> Maybe some bright person will prove me wrong by posting some working
>> information about how to get these apparently absent features working.
>
>
> Most people just use simple triggers to maintain aggregate summary
> tables...
>
> Chris
However, if (insert) triggers prove to be too much of a performance hit, try
cron'd functions that perform the aggregation for you. This system works well
for us, using the pk's (sequence) for start and stop points.
--
_______________________________
This e-mail may be privileged and/or confidential, and the sender does
not waive any related rights and obligations. Any distribution, use or
copying of this e-mail or the information it contains by other than an
intended recipient is unauthorized. If you received this e-mail in
error, please advise me (by return e-mail or otherwise) immediately.
_______________________________
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-05-11 15:03:43 | Re: Optimizer wrongly picks Nested Loop Left Join |
Previous Message | Tom Lane | 2005-05-11 14:18:34 | Re: Optimizer wrongly picks Nested Loop Left Join |