> > Ok, looks nice. But I am curious how this will work in the case when there are two (or more) errors in the same subscription, but different relations? >
We can't proceed unless the first error is resolved, so there shouldn't be multiple unresolved errors.
Ok. I thought multiple errors are possible when many tables are initialized using parallel workers (with max_sync_workers_per_subscription > 1).