How CloudNativePG manages physical replication slots for

How CloudNativePG manages physical replication slots for replication slot does not exist You can't remove a subscription database definition if there are subordinate subscriptions Remove the subscriptions first Problem Subscription does not exist replication slot postgres 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

replication slot postgres You must drop unused replication slots Failing to do so can lead to server unavailability How to drop a slot If you are not actively

replication slot does not exist You have to create publication before you create replication slot, otherwise you will see “publication does not exist” error The correct The main risk of using pg_basebackup without replication slots is to not be able to take a consistent backup as WAL segments may have been