if we have a refresh_schedule, then it's an MV, so we should also have an initial_as_of about materialize

[nrainer-materialize]

This occurred in the production sandbox.

[ggevay]

Ok, this should only occur for REFRESH MVs that were created before d474190 (the commit that added initial_as_of), i.e., mid February. The effect of the problem is that these MVs won't have mz_internal.mz_materialized_view_refreshes populated, but no other bad thing should happen.

There was one such MV in the production sandbox ("materialize"."public"."mv"). I've recreated this MV now.

There can be only one other environment where such MVs might theoretically occur, but even they have most probably recreated all their MVs many times since than.

So, I'm closing this issue in the hopes that it won't ever occur again.