Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
1.9.2.Final
-
None
-
False
-
None
-
False
Description
I'm trying to debug this issue, however from the log it is unclear which table has the CURRENT_TIMESTAMP (I've hundreds of tables).
│ 2022-09-17 14:42:40,598 INFO Postgres|source-prod_postgres_partition0|streaming REPLICA IDENTITY for 'myschema.mytable1' is 'DEFAULT'; UPDATE and DELETE events will contain previous values only for PK columns [io.debezium.connector.postgresql.PostgresSchema] │ │ 2022-09-17 14:42:40,598 INFO Postgres|source-prod_postgres_partition0|streaming REPLICA IDENTITY for 'myschema.mytable2' is 'FULL'; UPDATE AND DELETE events will contain the previous values of all the columns [io.debezium.connector.postgresql.PostgresSchema] │ │ 2022-09-17 14:42:40,599 WARN Postgres|source-prod_postgres_partition0|streaming Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamp'. Expression evaluation is not supported. [io.debezium.connector.postgresql.connection.PostgresDefaultValueConverter] │ │ 2022-09-17 14:42:40,599 WARN Postgres|source-prod_postgres_partition0|streaming Cannot parse column default value 'CURRENT_TIMESTAMP' to type 'timestamptz'. Expression evaluation is not supported. [io.debezium.connector.postgresql.connection.PostgresDefaultValueConverter]
Given it is part of the SQL standard, it would be probably nice to support it ( replacing it CURRENT_TIMESTAMP to CURRENT_TIMESTAMP(4) automatically?)
Should NOW() explicitly called out as supported in the guide?
