Yes, if you drop the replication slot and recreate it, Airbyte will perform a full refresh (initial sync) during the first run after reconfiguring the new slot for CDC. As mentioned in the [tutorial](https://airbyte.com/tutorials/incremental-change-data-capture-cdc-replication): > Be careful to not create the replication slot and publication before creating and populating your source table. If you do, Airbyte may send the source records twice to the destination. This duplication happens because on the initial synchronization, Airbyte effectively executes a full refresh, which uses SELECT statements on the source to retrieve records for replication. Then, for all subsequent syncs, it reads the transaction log (write-ahead log) for replication – however, because records sent in the initial sync were not sent based on events stored in the transaction log, the transaction log still contains a log of the creation of all of the records on the source, and so these records will be re-transmitted on the very next sync. So, when you recreate the replication slot and reconfigure Airbyte, it will perform an initial sync, effectively executing a full refresh.