Re: Many, many materialised views - Performance? - Mailing list pgsql-general

From Kevin Grittner
Subject Re: Many, many materialised views - Performance?
Date
Msg-id 1381284525.95722.YahooMailNeo@web162901.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: Many, many materialised views - Performance?  (Toby Corkindale <toby.corkindale@strategicdata.com.au>)
Responses Re: Many, many materialised views - Performance?  (Alban Hertroys <haramrae@gmail.com>)
Re: Many, many materialised views - Performance?  (Bill Moran <wmoran@potentialtech.com>)
List pgsql-general
Toby Corkindale <toby.corkindale@strategicdata.com.au> wrote:

> In this instance, we have a lot of queries that build certain aggregate
> results, which are very slow. The queries were initially all implemented
> as views, but then we started doing a type of materialising of our own,
> turning them into tables with CREATE TABLE AS SELECT ....
> This does make the results very fast to access now, but the side effect
> is a vast number of (very small) tables.

If you have multiple tables with identical layout but different
subsets of the data, you will probably get better performance by
putting them into a single table with indexes which allow you to
quickly search the smaller sets within the table.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-general by date:

Previous
From: Toby Corkindale
Date:
Subject: Re: Many, many materialised views - Performance?
Next
From: Adam Jelinek
Date:
Subject: Re: Hi, Friends, are there any ETL tools (free or commercial) available for PostgreSQL?