Connector getting Inactive due to replication slot PID already exists

creation of replication slot failed   Dan semua link slot

The problem turned out to be order-of-events The publication has to be created before the replication slot or else it will not find the

Replication slots for High Availability A replication slot exists solely on the instance that created it, and PostgreSQL does not replicate it on the standby Specifies the maximum number of replication slots that the server can support The default is 10

bonus new member 100% slot game SELECT * FROM pg_replication_slots to see if any replication slots were accidentally created that might be preventing WAL cleanup · SHOW Caused by: DebeziumException: Failed to start replication stream at LSN{B9DD22FBF0}; when setting up multiple connectors for the same database