Message-ID: <42821558.1010707@PresiNET.com>
Date: Wed, 11 May 2005 07:23:20 -0700
From: Bricklen Anderson <BAnderson@PresiNET.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050331)
MIME-Version: 1.0
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Sam Vilain <sam@vilain.net>, pgsql-performance@postgresql.org
Subject: Re: Prefetch
References: <200505100652.51401.molson@oceanconsulting.com>
	<42818B2E.8060403@vilain.net>
	<42818FB1.4060403@familyhealth.com.au>
In-Reply-To: <42818FB1.4060403@familyhealth.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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.
_______________________________