Re: Prefetch - Mailing list pgsql-performance

From Bricklen Anderson
Subject Re: Prefetch
Date
Msg-id 42821558.1010707@PresiNET.com
Whole thread Raw
In response to Re: Prefetch  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List 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.
_______________________________

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimizer wrongly picks Nested Loop Left Join
Next
From: Tom Lane
Date:
Subject: Re: Optimizer wrongly picks Nested Loop Left Join