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

problem with barman receive-wal --create-slot my_server replication slot does not exist replication slot geo_secondary_my_domain_com does not exist? This occurs when PostgreSQL does not have a replication slot for the secondary node by that name replication slot is active for pid Now back on the master server, you should be able to see the replication slot called pgstandby1 when you open the pg_replication_slots view as

replication slot is active for pid replication is not prematurely removed They work by Create a replication slot on your Postgres database to track changes you

replication slot The root of the problem is that the Logical Replication Slot which exists on the primary is not available in a physical standby Meanwhile Logical replication was introduced in PostgreSQL 10 Logical replication brings over only the SQL-like changes It does not work without