X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 8DA539DC84E for ; Mon, 16 Jan 2006 12:18:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 82811-02 for ; Mon, 16 Jan 2006 12:18:03 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.refusion.com (mail.refusion.com [213.144.155.20]) by postgresql.org (Postfix) with ESMTP id 617F89DC807 for ; Mon, 16 Jan 2006 12:18:01 -0400 (AST) Received: from iwing by mail.refusion.com (MDaemon.PRO.v8.1.4.R) with ESMTP id md50000478927.msg for ; Mon, 16 Jan 2006 17:16:39 +0100 Message-ID: <056a01c61ab8$63b70040$6402a8c0@iwing> From: To: "Michael Riess" , References: Subject: Re: Materialized Views Date: Mon, 16 Jan 2006 17:17:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-15"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.1830 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830 X-Authenticated-Sender: info@alternize.com X-Spam-Processed: mail.refusion.com, Mon, 16 Jan 2006 17:16:39 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 80.238.235.198 X-Return-Path: me@alternize.com X-MDaemon-Deliver-To: pgsql-performance@postgresql.org X-ClamAV: Pass X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=2.71 required=5 tests=[AWL=-0.713, DNS_FROM_RFC_DSN=2.872, NO_REAL_NAME=0.55, UNPARSEABLE_RELAY=0.001] X-Spam-Score: 2.71 X-Spam-Level: ** X-Archive-Number: 200601/200 X-Sequence-Number: 16678 hi mike > In particular I'm interested in a view which materializes whenever > queried, and is invalidated as soon as underlying data is changed. from the german pgsql list earlier last week: http://jonathangardner.net/PostgreSQL/materialized_views/matviews.html this seems to be pretty much what you want (except you'll have to update everything yourself). would be really nice if pgsql supports this "in-house" cheers, thomas