The problem

In some very rare cases during materialized view creation due to the way how it is created (table first and then fields) if another process accesses that table it can be cached improperly, without some fields, which may lead to improper working of the whole view (See related TS issue)

Solution

Need to make mat view creation process to be atomic.