pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedUsing materialized views for commonly-queried subsets
2+ messages / 2 participants
[nested] [flat]
* Using materialized views for commonly-queried subsets
@ 2006-03-10 02:25 Casey Allen Shobe <lists@seattleserver.com>
2006-03-10 15:17 ` Re: Using materialized views for commonly-queried subsets Jim C. Nasby <jnasby@pervasive.com>
0 siblings, 1 reply; 2+ messages in thread
From: Casey Allen Shobe @ 2006-03-10 02:25 UTC (permalink / raw)
To: 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@seattleserver.com | 206-381-2800
SeattleServer.com, Inc. | http://www.seattleserver.com
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Using materialized views for commonly-queried subsets
2006-03-10 02:25 Using materialized views for commonly-queried subsets Casey Allen Shobe <lists@seattleserver.com>
@ 2006-03-10 15:17 ` Jim C. Nasby <jnasby@pervasive.com>
0 siblings, 0 replies; 2+ messages in thread
From: Jim C. Nasby @ 2006-03-10 15:17 UTC (permalink / raw)
To: Casey Allen Shobe <lists@seattleserver.com>; +Cc: pgsql-performance
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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2006-03-10 15:17 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-03-10 02:25 Using materialized views for commonly-queried subsets Casey Allen Shobe <lists@seattleserver.com>
2006-03-10 15:17 ` Jim C. Nasby <jnasby@pervasive.com>
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