Message-ID: <403B8C89.5010904@cybertec.at>
Date: Tue, 24 Feb 2004 18:40:25 +0100
From: =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <postgres@cybertec.at>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
MIME-Version: 1.0
To: Richard Huxton <dev@archonet.com>
Cc: "Jonathan M. Gardner" <jgardner@jonathangardner.net>,
	pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org,
	pgsql-performance@postgresql.org
Subject: Re: [HACKERS] [SQL] Materialized View Summary
References: <200402240811.13013.jgardner@jonathangardner.net>
	<200402241711.20947.dev@archonet.com>
In-Reply-To: <200402241711.20947.dev@archonet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Richard Huxton wrote:
> 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.
> 


Are there any plans to rewrite that in C and add proper support for SQL 
commands? (e.g. "CREATE MATERIALIZED VIEW", "DROP VIEW", ...).


	Best regards,

		Hans

-- 
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/2952/30706 or +43/664/233 90 75
www.cybertec.at, www.postgresql.at, kernel.cybertec.at