if you're looking at pg materialized views, look at listen/notify too. so, the builder Listens and write queries then Notify, so re-do the m-view? or just use

if you're looking at pg materialized views, look at listen/notify too. so, the builder Listens and write queries then Notify, so re-do the m-view? or just use Notify with good payload after each write you think is important? (I use this sometimes) I mean, a trigger to push could work, yea? or, some clever rig with pg-logical replication (I'd have to think on this one more, may be crap)