> By default, materialized views in PostgreSQL are not automatically refreshed. If the underlying data changes, the materialized view remains stale until it's refreshed.
Can’t this be somewhat alleviated by running a job native on Postgres or some external one to refresh the views on a schedule? It’s not ideal or realtime but better than having it done as-hoc.
Yeah but then it’s just lipstick on a pig. I can already create a regular table and update it myself.
If my RBDMS adds materialized views, I want it to help me with it lol
Rewriting a large view based on hundreds of gb of rows sounds like a recipe for a possible outage in an OLTP situation.