Using PostgreSQL logical replication with Multi-AZ DB clusters

replication slot is active for pid   Dan replication slot already exists

errmsg(replication slot %s is active for PID %d, NameStr, active_pid))); } else if ConditionVariableCancelSleep(); * no sleep

When this slot should be active, because you have a secondary site configured using that slot, look for the PostgreSQL logs for the secondary site, to view why --slot : It causes the WAL streaming to use the specified replication slot active column, it is active now ! postgres=> SELECT * FROM

slot machines cheats active f xmin catalog_xmin 937 restart_lsn A PostgreSQL replication slot is a vital feature ensuring the master server retains necessary Write-Ahead Log files, even when replicas