It's obvious why un*analyzed* tables could cause materialization to be
slow, but why would un*vacuumed* tables cause slowness when creating
materialized views?
Also, how can you be sure that the underlying tables have been analyzed
before pg_restore gets to the CREATE MATERIALIZED VIEW statements?
On Sun, Jul 28, 2024 at 12:36 PM Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
wrote:
> fwiw, we have a lot of materialized views, so restoring a DB on
> non-vacuumed tables caused the materialization to take a lot longer than it
> would have with autovacuum running as normal. Seems worth experimenting
> though.
>