From: Jim C. Nasby <jnasby@pervasive.com>
To: Casey Allen Shobe <lists@seattleserver.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Using materialized views for commonly-queried subsets
Date: Fri, 10 Mar 2006 09:17:37 -0600
Message-ID: <20060310151737.GF45250@pervasive.com> (raw)
In-Reply-To: <200603100225.08152.lists@seattleserver.com>
References: <200603100225.08152.lists@seattleserver.com>
See also
http://www.jonathangardner.net/PostgreSQL/materialized_views/matviews.html
On Fri, Mar 10, 2006 at 02:25:08AM +0000, Casey Allen Shobe wrote:
> I typed up a description of a situation where the only viable option to
> improve performance was to use a materialized view, which, when implemented,
> was found to improve performance twenty-sevenfold, even with a fairly small
> amount of excess data (which is antipated to grow). I thought this might be
> of use to anybody else in a similar situation, so I thought I'd post it here.
>
> http://community.seattleserver.com/viewtopic.php?t=11
>
> Feel free to reproduce as you see fit.
>
> Cheers,
> --
> Casey Allen Shobe | cshobe@seattleserver.com | 206-381-2800
> SeattleServer.com, Inc. | http://www.seattleserver.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, lists@seattleserver.com
Subject: Re: Using materialized views for commonly-queried subsets
In-Reply-To: <20060310151737.GF45250@pervasive.com>
* 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