Re: how to create materialized view in postgresql 8.3 - Mailing list pgsql-general

From Michael Paquier
Subject Re: how to create materialized view in postgresql 8.3
Date
Msg-id CAB7nPqQ8zGUnoVtJObD3HZX5pv57YrBvss5Unam8mgfniY2kYg@mail.gmail.com
Whole thread Raw
In response to Re: how to create materialized view in postgresql 8.3  (Vincent Veyron <vv.lists@wanadoo.fr>)
List pgsql-general



On Wed, Apr 10, 2013 at 10:33 PM, Vincent Veyron <vv.lists@wanadoo.fr> wrote:
I find this rather surprising, considering the fact that a properly
tuned database will return queries over millions of rows and multiple
joins in milliseconds, given the proper hardware.

I can see how a datawharehouse with terrabytes of data can make use of
them, but that is hardly a common situation. It seems to me many of
these people clamouring for materialized views would be better off
simply using a proprer data structure (and taking a few SQL courses).

Am I misguided?
A use case of materialized views is cache for web application where you could refresh them with complicated join queries running in background. You cannot do that with a view as it would be necessary to reprocess the query each time, and it is difficult to do that with only tables as this could incredibly complicate your database schema.
--
Michael

pgsql-general by date:

Previous
From: Vincent Veyron
Date:
Subject: Re: how to create materialized view in postgresql 8.3
Next
From: Michael Paquier
Date:
Subject: Re: how to find which tables required indexes in postgresql