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

Postgres Connector inconsistent handling of timestamp precision

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 0.7.5
    • Fix Version/s: 0.8.0.Beta1
    • Component/s: postgresql-connector
    • Labels:
      None
    • Environment:

      PostgreSQL 9.6.8
      Debezium 0.7.5
      Decoderbufs plugin

      Description

      We have noticed inconsistent behaviour in how timestamp precision is preserved by Debezium during snapshotting vs. normal CDC operations on the Postgres connector.

      For example on a DB field of type:

      timestamp without time zone
      

      containing value:

      2018-03-28 12:03:35.406753
      

      during a snapshot we get:

      1522238615406000000 (notice loss of nanosecond precision)
      

      However, if we update the same record we get:

      1522238615406753000 (no loss of nanosecond precision)
      

      We are not setting time.precision.mode in our config (so it should default to adaptive). We should see full nanosecond precision during both the snapshot and normal CDC.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jpechanec Jiri Pechanec
                Reporter:
                jsyvanen Julius Syvanen
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: