Postgres server not starting due to already active replication slot

Postgres server not starting due to already active replication slot replication slot already exists vCenter Server Appliance fails with the error: FATAL: remaining connection slots are reserved for non-replication superuser connections book replication slot already exists PostgreSQL's logical decoding uses replication slots First, you configure the replication slot: If the publication already exists (either for all

replication slot already exists replication table > synchronization worker for subscription slot > pg_37986_sync_37922_7210774007126708177 already exists

replication slot does not exist my_slot replication slot, with the replication slots, check if the slot already exists or if there's a conflict with slot names  slots This is a perfect match for the use of temporary replication slots as many users are already using the stream mode of pg_basebackup