-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
What Debezium connector do you use and what version?
debezium-connector-postgres-1.9.0.Final
What is the connector configuration?
{ "connector.class": "io.debezium.connector.postgresql.PostgresConnector", "tasks.max": "1", "database.hostname": "postgres", "database.port": "5432", "database.user": "postgres", "database.password": "postgres", "database.dbname" : "postgres", "database.server.name": "dbserver3", "slot.name":"dbserver3", "schema.include.list": "inventory", "key.converter": "io.confluent.connect.avro.AvroConverter", "key.converter.schemas.enable": "true", "key.converter.schema.registry.url": "http://schema-registry:8081", "value.converter": "io.confluent.connect.avro.AvroConverter", "value.converter.schemas.enable": "true", "value.converter.schema.registry.url": "http://schema-registry:8081" }
What is the captured database version and mode of deployment?
First encountered the issue in RDS but I can reproduce using your example repository:
So Postgres 14.2
What behaviour do you expect?
When adding a text column with a default value, like this:
alter table inventory.customers add column some_txt text not null default 'hello';
and inserting a new row, using the schema registry UI you can see the schema being updated:
But if you do the same thing with an enum then you do not get a default value:
CREATE TYPE activity AS ENUM ('active', 'inactive'); alter table inventory.customers add column activity activity not null default 'active'::activity;
This is particularly problematic when trying to add an enum to a schema that's configured with a FULL compatibility level.
Do you see the same behaviour using the latest relesead Debezium version?
Haven't tried it but I do not see anything in the changelog that would indicate this issue is fixed.
- is cloned by
-
DBZ-5853 PostgreSQL range default values are missing from generated schema
- Closed