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

group_concat_max_len should be stored in the binary log

Details

    • Task
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • None
    • Replication
    • None

    Description

      If statement based replication is enabled and a GROUP_CONCAT value is used, the data can get inconsistent on the slave. if the slave's value is lower.

      I think group_concat_max_len should be stored in the binary log.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8294 Inconsistent behavior of slave parallel threads at runtime

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8291 Parallel replication causes slave threads to not pick up new global config after restart

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-9474 group_concat_max_len not being read from /etc/my.cnf

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            Converted to a feature request.

            Sadly, there are many variables which can cause data inconsistency if they are set to different values on master and slave. group_concat_max_len alone won't really make so much difference.

            elenst Elena Stepanova added a comment - Converted to a feature request. Sadly, there are many variables which can cause data inconsistency if they are set to different values on master and slave. group_concat_max_len alone won't really make so much difference.
            michaeldg Michaël de groot added a comment -

            Maybe it's an idea to convert all of these to subtasks of 1 so the community can add variables and do a per-case decision what should be done with it?

            michaeldg Michaël de groot added a comment - Maybe it's an idea to convert all of these to subtasks of 1 so the community can add variables and do a per-case decision what should be done with it?
            serg Sergei Golubchik added a comment -

            The good list of these variables can found in the query cache code. Query cache should know when a variable affects the result so it tracks them all. And because it's completely internal in-memory structure it can be changed to track more variables with no compatibility or interoperability effects. That's why it tracks quite a few of them.

            serg Sergei Golubchik added a comment - The good list of these variables can found in the query cache code. Query cache should know when a variable affects the result so it tracks them all. And because it's completely internal in-memory structure it can be changed to track more variables with no compatibility or interoperability effects. That's why it tracks quite a few of them.

            People

              Unassigned Unassigned
              michaeldg Michaël de groot
              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.