From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> |
Cc: | Mike Christensen <mike(at)kitchenpc(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: how to create materialized view in postgresql 8.3 |
Date: | 2013-04-10 14:05:25 |
Message-ID: | CAB7nPqQ8zGUnoVtJObD3HZX5pv57YrBvss5Unam8mgfniY2kYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Apr 10, 2013 at 10:33 PM, Vincent Veyron <vv(dot)lists(at)wanadoo(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-04-10 14:11:09 | Re: how to find which tables required indexes in postgresql |
Previous Message | Vincent Veyron | 2013-04-10 13:33:01 | Re: how to create materialized view in postgresql 8.3 |