Postgres configuration slot.drop.on.stop doesn't work during Snapshot [DBZ-3524]
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 6
- Forks
- 9
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-3524](https://issues.redhat.com/browse/DBZ-3524)
We have observed that the Postgres configuration [{{slot.drop.on.stop}}|https://debezium.io/documentation/reference/connectors/postgresql.html#postgresql-property-slot-drop-on-stop] doesn't actually drop the slot if you delete the connector during the snapshot phase. It is only if the connector gets to the streaming phase will it drop the slot when you delete the connector.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the PostgreSQL connector documentation for `slot.drop.on.stop` linked in the issue, then trace how connector deletion handles cleanup during the snapshot phase. Done means deleting the connector during a snapshot drops the slot, as it does after streaming begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100