Local replication slot does not exist after initial sync

Local replication slot does not exist after initial sync replication slot does not exist If the replication slot is created after data is inserted and the publication is created, then it works We just can't tell Patroni to not create it until some replication slot already exists In essence, the primary server has the ability to recycle the WAL if the primary no longer requires it What if, however, the replica has not yet eaten it? The

replication slot already exists replication slot zoo does not exist References PostgreSQL documentation: Replication Management Functions Categories Replication, Replication slots

replication slot does not exist If you do see the slot under the slot_name column, check the database column This should match the database that you have added in the setup form The solution Replication slots were introduced in PostgreSQL to help ensure a primary PostgreSQL instance does not remove WAL files before a replica has