Using materialized views for commonly-queried subsets

From: Casey Allen Shobe <lists(at)seattleserver(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Using materialized views for commonly-queried subsets
Date: 2006-03-10 02:25:08
Message-ID: 200603100225.08152.lists@seattleserver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)seattleserver(dot)com | 206-381-2800
SeattleServer.com, Inc. | http://www.seattleserver.com

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message NbForYou 2006-03-10 07:11:44 Process Time X200
Previous Message Jan de Visser 2006-03-10 02:00:27 Re: Hanging queries on dual CPU windows