> With this patch, I observed that replication origins whose remote_lsn
> is '0/00000000' are not present on the upgraded node when
> max_logical_replication_workers is set to 0.
> Is this behaviour expected?
Small clarification: I meant that the replication origins whose
remote_lsn was 0/00000000 before the upgrade are not present in
pg_replication_origin_status on the upgraded node. The replication
origin entries themselves still exist in pg_replication_origin


Reply via email to