Postgresql replication slot used by barman has a long replay_lag

I want to set up replication between two of my databases One is an Aurora database in PG 10 the publisher, and the other one is an RDS database

Postgresql replication slot used by barman has a long replay_lag replication slot slot_name is already active for PID x providing immediate feedback While using the pglogical extension, you can only use the cluster

I want to set up replication between two of my databases One is an Aurora database in PG 10 the publisher, and the other one is an RDS database

replication slot already exists pid 42435 usesysid 16384 usename Replication 대상 Database는 postgres입니다 현재 Replication Slot은 Active

PID holding the lock , and whether the lock has been globally One replication slot per active BDR peer; One group replication slot For

replication slot is active for pid Hello, I have created a stream to migrate data from Cloud SQL Postgresql to BigQuery, and it has been working pretty well for a few months

Make logical replication slots survive failoverswitchover on PostgreSQL v11+ The replication slot if copied from the primary to the replica with restart and