conduktor.io ↗
← All errors
high PostgreSQL Replication

ERROR: replication slot "debezium" already exists

Root cause

An attempted slot creation found an existing name. Existing slots can be normal on restart; inspect ownership, plugin, database, saved offsets and competing connector instances before changing anything.

How to fix

  1. Inspect pg_replication_slots and the connector’s slot.name, plugin.name, database and offsets. Stop an unintended competing reader before reconnecting.
  2. Reuse a compatible retained slot when the connector’s documented resume path permits it. Slot deletion is a recovery decision, not the default response to this message.
⚠ Dropping a slot removes its WAL-retention protection and resume position. Establish a recovery/reconciliation plan first; slot.drop.on.stop is intended for test/development use.

Recovery guidance reviewed 2026-10-27 against v3.7.0.Final.

Official Debezium documentation ↗