Should a materialized view be based on a view? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Should a materialized view be based on a view?
Date
Msg-id 4EC68743020000250004327B@gw.wicourts.gov
Whole thread Raw
Responses Re: Should a materialized view be based on a view?
Re: Should a materialized view be based on a view?
List pgsql-hackers
I still have a lot of reading to do before I propose anything
concrete for development, but one thing that has already struck me
as a common theme for MVs is that a lot of people seem to like the
idea of first creating a "normal" view, and then materializing it. 
That seems pretty attractive to me, too.  How do people feel about
that as a fundamental design decision: that a MV would always have
a corresponding view (under a different name or in a different
schema)?  Love it or hate it?
-Kevin


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Inlining comparators as a performance optimisation
Next
From: Andres Freund
Date:
Subject: Re: testing ProcArrayLock patches