My understanding and hope was that Mat Views cache their data and that is how they are so fast. But we are experience “cancelling statement due to conflict with recovery” errors on MV’s with large data sets and I thought that this could only happen if we ran the underlying query, not the Mat View?
Have I got it wrong??
A materialized view is, physically, just like any other table. It is a cache but only in the sense that tables cache real life data.
