From: Sanjay Arora <skpobox@gawab.com>
To: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Hardware upgrade for a high-traffic database
Date: 11 Aug 2004 21:17:10 +0530
Message-ID: <1092239230.2277.5.camel@Sewak.Asr.Lan> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A7449@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A7449@Herge.rcsinc.local>
On Wed, 2004-08-11 at 17:51, Merlin Moncure wrote:
> One thing you might consider is materialized views. Your aggregate
> functions are killing you...try to avoid using them (except min/max on
> an index). Just watch out for mutable functions like now().
>
> http://www.varlena.com/varlena/GeneralBits/Tidbits/matviews.html
>
> An application specific approach is to use triggers to keep the data you
> need in as close to query form as possible...you can reap enormous
> savings particularly if your queries involve 3 or more tables or have
> large aggregate scans.
I thought materialized views support in pgsql was experimental as yet.
Are the pg mat-view code upto production servers? Also, do you have to
delete mat-views before you dump the db or does dump automatically not
dump the mat-views data?
Sanjay.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: skpobox@gawab.com
Subject: Re: Hardware upgrade for a high-traffic database
In-Reply-To: <1092239230.2277.5.camel@Sewak.Asr.Lan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox