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

[debezium] ERROR: option \"include-unchanged-toast\" = \"0\" is unknown

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 0.9.0.CR1
    • 0.9.0.Beta2
    • postgresql-connector
    • None

    Description

      Seams like wal2json plugin removed include-unchanged-toast:

      https://github.com/eulerto/wal2json/commit/66d836d209f71f2337ea622ae63669d759e30926#diff-7cc6c09e7ed49666951d3bd508952c52
      https://github.com/eulerto/wal2json/commit/2e6384cdfe9e97ece59596b2b46384ed6d248bba#diff-7cc6c09e7ed49666951d3bd508952c52

      I'm now running on AWS RDS 10.4 Postgres and when creating connector i get:

      org.apache.kafka.connect.errors.ConnectException: org.postgresql.util.PSQLException: ERROR: option \"include-unchanged-toast\" = \"0\" is unknown
        Where: slot \"xxxxxxxxxxx\", output plugin \"wal2json\", in the startup callback
      	at io.debezium.connector.postgresql.RecordsStreamProducer.start(RecordsStreamProducer.java:119)
      	at io.debezium.connector.postgresql.PostgresConnectorTask.start(PostgresConnectorTask.java:126)
      	at io.debezium.connector.common.BaseSourceTask.start(BaseSourceTask.java:47)
      	at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:198)
      	at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)
      	at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Caused by: org.postgresql.util.PSQLException: ERROR: option \"include-unchanged-toast\" = \"0\" is unknown
        Where: slot \"xxxxxxxxxxxx\", output plugin \"wal2json\", in the startup callback
      	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440)
      	at org.postgresql.core.v3.QueryExecutorImpl.processCopyResults(QueryExecutorImpl.java:1116)
      	at org.postgresql.core.v3.QueryExecutorImpl.writeToCopy(QueryExecutorImpl.java:998)
      	at org.postgresql.core.v3.CopyDualImpl.writeToCopy(CopyDualImpl.java:19)
      	at org.postgresql.core.v3.replication.V3PGReplicationStream.updateStatusInternal(V3PGReplicationStream.java:189)
      	at org.postgresql.core.v3.replication.V3PGReplicationStream.forceUpdateStatus(V3PGReplicationStream.java:109)
      	at io.debezium.connector.postgresql.connection.PostgresReplicationConnection.startPgReplicationStream(PostgresReplicationConnection.java:305)
      	at io.debezium.connector.postgresql.connection.PostgresReplicationConnection.createReplicationStream(PostgresReplicationConnection.java:195)
      	at io.debezium.connector.postgresql.connection.PostgresReplicationConnection.startStreaming(PostgresReplicationConnection.java:179)
      	at io.debezium.connector.postgresql.RecordsStreamProducer.start(RecordsStreamProducer.java:105)
      	... 10 more
      

      Seams like this pull request introduced bug:
      https://github.com/debezium/debezium/commit/94c0a42286d3359f718620092619f921fc924dcb#diff-77ee0f8ecffcd58e3f29e08fd55dc9d6

      Attachments

        Issue Links

          Activity

            People

              jpechane Jiri Pechanec
              robert.pofuk Robert Pofuk (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: