Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-31770

Non-full binary log row image for INSERT ... ON DUPLICATE KEY UPDATE

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2.44, 11.0.2, 10.3.39, 10.8.8, 10.4.30, 10.7, 10.5.21, 10.6.14, 10.9.7, 10.10.5, 10.11.4
    • 10.4, 10.5, 10.6, 10.11
    • Replication
    • None

    Description

      I assume, for server with configuration

      binlog-format=MIXED
      binlog-row-image=FULL

      there is an issue with non-full binary log representation for at least INSERT and UPDATE statements when "ON DUPLICATE KEY UPDATE" is used which was described in https://jira.mariadb.org/browse/MDEV-21810 and https://jira.mariadb.org/browse/MDEV-28310.

      As far as I can see, examples from those tickets still produce non-full binary log result on checked 10.2 - 11.0 versions currently.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21810 MBR: Unexpected "Unsafe statement" warning and use of non-full image with binlog_row_image=FULL

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28310 Missing binlog data for INSERT .. ON DUPLICATE KEY UPDATE

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              Elkin Andrei Elkin
              dn Dmitry
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.