Many REFRESH MATERIALIZED VIEW at publisher causes out of disk space

[dusatvoj]

Hello,
I have database which I want to replicate to another cluster.
I created replication and added all tables from public schema.

select pglogical.replication_set_add_all_tables('default', ARRAY['public'],true);

In other schema are materialized views, created from tables in public. The MV are refreshing every hour.

Now I have to stop replication due to a problem that MVs are not recognized correctly by pglogical and LSN is not updated in replication slot and this causes out of disk space.

(at monitoring, you can see that everything looks fine but the MVs are dealbreaker)

---

Am I doing anything wrong? Do I have to add replication also to other schemas?