Connector getting Inactive due to replication slot PID already exists

io debezium debeziumexception_ creation of replication slot failed   Dan situs slot gacor deposit 10 ribu

TIP: If the query fails, it indicates that replication is not in place Go to the Setup tab of the connector, and click the Re-sync All Historical Data link

Caused by: DebeziumException: Creation of replication slot failed Caused by: : ERROR: could not Debezium Connector is used to capture row-level changes and publish them as Events to your Kafka Cluster without the need to write custom

naga 33 88 slot Logical decoding – on which logical replication and Debezium depend on – requires wal_level configuration parameter to be set to “logical”, and Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write