Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-5204

Debezium Postgres v1.9.3 fails in Materialize CI

XMLWordPrintable

    • False
    • None
    • False
    • Hide

      You'll need Docker installed. Then run:

       

      docker pull debezium/connect:1.9

      git clone https://github.com/MaterializeInc/materialize.git

      git checkout 6005b6041

      cd test/debezium

      ./mzcompose run postgres

       

      Show
      You'll need Docker installed. Then run:   docker pull debezium/connect:1.9 git clone https://github.com/MaterializeInc/materialize.git git checkout 6005b6041 cd test/debezium ./mzcompose run postgres  

      What Debezium connector do you use and what version?

      PostgreSQL v1.9.3.Final

      What is the connector configuration?

      https://github.com/MaterializeInc/materialize/blob/8b98fccc493381eccfd19778bd08bd4b3c971dd8/test/debezium/postgres/debezium-postgres.td.initialize#L41-L60

      What is the captured database version and mode of depoyment?

      v10 in Docker

      What behaviour do you expect?

      Debezium is successfully able to ingest data from a table with an enum type it has not seen before.

      What behaviour do you see?

      Debezium crashes with the following error message:

      org.apache.kafka.connect.errors.ConnectException: Database connection failed during resolving unknown type

      ...

      Caused by: org.postgresql.util.PSQLException: This connection has been closed.

       

      This behavior is new in v1.9.3.Final and was not present in v1.9.2.Final.

      Note that the database has not crashed. PostgreSQL query logs show that the type resolution query was successfully prepared and executed by Debezium. Something is being mishandled on the Debezium side.

      Do you see the same behaviour using the latest relesead Debezium version?

      Yes, it's new in v1.9.2.Final.

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      Yes, in the same gist: https://gist.github.com/benesch/b71ba0bdb8f8d6e038ee241f0ef0f9c0

              Unassigned Unassigned
              benesch Nikhil Benesch (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: