The Insatiable Postgres Replication Slot

The Insatiable Postgres Replication Slot replication slot is active for pid Postgres prevents active slots from being dropped If it does happen , PowerSync would replication slot already exists pid terminated,application_controller,{application_start_failure,realtime,{{shutdown,{failed_to_start_child,' Replication',{{badmatch

replication slot already exists production environment that unable to get around to apply There are two ERROR messages observed here 'replication slot is active for PID'

replication slot is active for pid When Kafka Connect attempts to restart the connector too quickly, the database sees that the slot is still active although the client has disconnected Hope PID holding the lock , and whether the lock has been globally One replication slot per active BDR peer; One group replication slot For