Using PostgreSQL Logical Replication to Maintain an Always Up-to

error_ replication slot is active for pid   Dan error slot

slot_name my_pub1 plugin pgoutput slot_type logical datoid 16401 database db temporary f active t active_pid

Failing to do so will make the replication slot stuck at its current position, the publisher node will start accumulating WALs and inevitably Monitoring Replication Slots Each BDR node keeps: One replication slot per active BDR peer; One group replication slot For example: Toggle Wrap Copy bdrdb

slot meta download ERROR: executing recovery, execution of command failed at 1st stage pid 28665: LOG: starting recovering node 0 > 10:04 error saying the replication slot is already in use Here is the Powered by Discourse, best viewed with JavaScript enabled