On 9/15/15 2:14 AM, Johann Spies wrote:
> What are the pro's and con's of large materialized views vs. tables in a
> case like this?
AFAIK a matview is essentially the same as a table under the covers, so
I don't believe there's any reason not to use one. At some point we'll
have incremental refresh of some sort, which might help in your case.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
