> My understanding is that they require running & storing the full query. This is right. Having a single materialized view containing nested queries is not a g

> My understanding is that they require running & storing the full query. This is right. Having a single materialized view containing nested queries is not a good idea. But you can factor out the nested queries into their own materialized views. The propagation of updates between materialized views can achieve an effect similar to that of complex triggers. I should've been more careful with my original comment, though. I'm not saying triggers are worthless. But, whenever a materialized view can do the job, it's usually preferable.