problem with barman receive-wal --create-slot my_server

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

You must drop the logical replication slot in the primary server if the corresponding subscriber no longer exists Otherwise, the WAL files

replication slot postgres A limitation of the PostgreSQL implementation is that replication slots are not cluster-aware: a replication slot exists solely on the instance

replication slot does not exist The script attempts to create the replication slot automatically if it does not exist If you're repurposing an old site into a Geo secondary site, you must add