From: Richard Huxton <dev@archonet.com>
To: "Jonathan M. Gardner" <jgardner@jonathangardner.net>,
	pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org,
	pgsql-performance@postgresql.org
Subject: Re: [SQL] Materialized View Summary
Date: Tue, 24 Feb 2004 17:11:20 +0000
User-Agent: KMail/1.5
References: <200402240811.13013.jgardner@jonathangardner.net>
In-Reply-To: <200402240811.13013.jgardner@jonathangardner.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402241711.20947.dev@archonet.com>

On Tuesday 24 February 2004 16:11, Jonathan M. Gardner wrote:
>
> I've written a summary of my findings on implementing and using
> materialized views in PostgreSQL. I've already deployed eagerly updating
> materialized views on several views in a production environment for a
> company called RedWeek: http://redweek.com/. As a result, some queries
> that were taking longer than 30 seconds to run now run in a fraction of a
> millisecond.
>
> You can view my summary at
> http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html

Interesting (and well written) summary. Even if not a "built in" feature, I'm 
sure that plenty of people will find this useful. Make sure it gets linked to 
from techdocs.

If you could identify candidate keys on a view, you could conceivably automate 
the process even more. That's got to be possible in some cases, but I'm not 
sure how difficult it is to do in all cases.

-- 
  Richard Huxton
  Archonet Ltd