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

Annotate_rows written in a 'random' position

    XMLWordPrintable

Details

    • Unexpected results
    • Hide
      Ensure that Annotate_rows is always written direct after GTID information,
      before any table_map events. Before this patch the event could be written in a random position in the binary log. This change make the place of the Annotate_rows event predictable.

      When mixing transactional and not transactional tables in the same transaction, the Annotate rows event was not always written in the
      case of a rollback. This is now fixed.
      Show
      Ensure that Annotate_rows is always written direct after GTID information, before any table_map events. Before this patch the event could be written in a random position in the binary log. This change make the place of the Annotate_rows event predictable. When mixing transactional and not transactional tables in the same transaction, the Annotate rows event was not always written in the case of a rollback. This is now fixed.

    Description

      Annotate_rows event are written in a 'random' position if one combines non transactional and transactional tables.

      This can be seen in the test rpl.rpl_mixed_mixing_engines

      This can be fixed by writing the Annotate_rows event into the non transactional cache if there are table maps that are not transactional. If not, write the event into the transactional cache.
      This ensures that the Annotate_rows event is always written to the binary log before any table map events.

      Attachments

        Issue Links

          Activity

            People

              monty Michael Widenius
              monty Michael Widenius
              Votes:
              0 Vote for this issue
              Watchers:
              7 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.