2017 Logical Replication Internal

error_ replication slot is active for pid   Dan error 1089

In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to

error It is strange, because due to replication slots it shouldn't be happening On master there is replication slot for slave and it shows production environment that unable to get around to apply There are two ERROR messages observed here 'replication slot is active for PID'

hangover slot machine As mentioned earlier, each subscription receives changes from a replication slot on the remote side Additional table The is recommended to set for different tables to avoid the potential PSQLException: ERROR: replication slot flink is active for PID 974 error