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

FULL_NODUP mode for binlog_row_image

    XMLWordPrintable

Details

    Description

      With FULL_NODUP mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.

      FULL_NODUP is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated.

      This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803)

      (Note that originally the MDEV was referring to the original Alibaba option, FULL_DIFFERENT. This was changed to FULL_NODUP to reflect the option implemented in MariaDB).

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33049 Assertion `marked_for_write_or_computed()' failed in bool Field_new_decimal::store_value(const my_decimal*, int*)

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-32894 mysqlbinlog flashback support binlog_row_image FULL_NODUP mode

          • Major - Major loss of function.
          • Closed

          Activity

            People

              TheLinuxJedi Andrew Hutchings
              TheLinuxJedi Andrew Hutchings
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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