-
Bug
-
Resolution: Won't Do
-
Critical
-
None
-
1.9.5.Final
-
None
-
False
-
None
-
False
-
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
PostgreSQL connector and docker debezium/connect:latest (1.9.5.Final)
What is the connector configuration?
docker run -d --name connect -p 8083:8083 --link kafka:kafka -e BOOTSTRAP_SERVERS=kafka:9092 -e GROUP_ID=sonae_group -e CONFIG_STORAGE_TOPIC=sonae_storage_topic -e OFFSET_STORAGE_TOPIC=sonae_offset_topic debezium/connect:latest
{
"name": "store1",
"config":
}
What is the captured database version and mode of depoyment?
On-premises PostgreSQL database version 9.4.21.
What behaviour do you expect?
Debezium 1.9 should still work with PG 9.6 (or 9.4.21 in my case) which doesn't have the function call array_position.
What behaviour do you see?
The issue here is that a function call is being used in the connection validation, array_position, seen here and this function is only compatible on PG 10+.
This was changed in DBZ-4710. It probably should not have added this as a part of Debezium 1.9. It makes sense for Debezium 2.0 since I believe PG10+ is being targetted in that new major version.
Do you see the same behaviour using the latest relesead Debezium version?
Yes.
Do you have the connector logs, ideally from start till finish?
Yes.
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
Usage of the Debezium PostgreSQL connector on databases with in a version (9.6 for example) that doesn't have the array_position function available.
- is caused by
-
DBZ-4710 Replication role check on RDS Postgres fails
- Closed