Re: Optimizations - Mailing list pgsql-general

From Craig Ringer
Subject Re: Optimizations
Date
Msg-id 4B91B1C5.3000707@postnewspapers.com.au
Whole thread Raw
In response to Re: Optimizations  (Ogden <lists@darkstatic.com>)
List pgsql-general
On 5/03/2010 10:09 PM, Ogden wrote:

> Would searching a huge table be as fast as calculating or about the same? I'll have to run some tests on my end but I
amvery impressed by the speed of which PostgreSQL executes aggregate functions. 

I'm not sure what you're asking.

> Do you suggest looking at this option when we see the reporting to slow down? At that point do you suggest we go back
tothe drawing board? 

If it ain't broke, don't fix it. However, it's a good idea to make it
easy to fix later - for example, wrap your score calculations up into a
view (see CREATE VIEW) so that you can replace it with a materialized
view later if you start seeing performance issues.

--
Craig Ringer

pgsql-general by date:

Previous
From: "Wang, Mary Y"
Date:
Subject: What's the best way to deal with the pk_seq sequence value after a restore (bulk loading)?
Next
From: Noah Misch
Date:
Subject: 9.0 VACUUM FULL vs. ALTER TABLE?