Postgres connector failed after update connector to use custom Postgres publication(create manually) [DBZ-2314]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-2314](https://issues.redhat.com/browse/DBZ-2314)
scenario to reproduce:
# create Postgres connector with default publication name and default publication auto create mode.
# create custom publication 'test_publication' for a specific table(in addition to Debezium default publication )
# update connector publication name to 'test_publication'
The connector task will be on a Failed state. Initializing PGReplicationStream will throw an error 'publication "test_publication" does not exist Where: slot "connector_slot", output plugin "pgoutput", in the change callback, associated LSN 0/3DBD078"
Contributor guide
Research direction
Reproduce the three-step connector scenario, including the manually created test_publication and the publication-name update. Start at PGReplicationStream initialization and investigate why the connector reports that the publication does not exist; done means the updated connector task no longer enters Failed state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100