See also
http://www.jonathangardner.net/PostgreSQL/materialized_views/matviews.html
On Fri, Mar 10, 2006 at 02:25:08AM +, 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 | [EMAIL PROTECTED] | 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 [EMAIL PROTECTED]
Pervasive Software http://pervasive.comwork: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---(end of broadcast)---
TIP 6: explain analyze is your friend
