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

GLOBAL debug_dbug setting affected by collation_connection=utf16…

Details

    Description

      SET collation_connection=utf16le_general_ci;
      SET GLOBAL debug_dbug='d,any_random_string';
      

      Will add about 8000-11000 lines of debug information to the error log. However,

      SET GLOBAL debug_dbug='d,any_random_string';
      

      Does not. Happens on all 10.2-10.9 debug versions. Tested via CLI only.

      Discussed with bar and marko.

      Attachments

        Activity

          The problem happens because Sys_var_dbug::do_check() does not convert the value to utf8.
          The problem is also repeatable with this script:

          SET collation_connection=utf16le_general_ci;
          SET  debug_dbug='d,any_random_string';
          SELECT @@debug_dbug;
          

          +--------------+
          | @@debug_dbug |
          +--------------+
          | d            |
          +--------------+
          

          This method should fix fixed to convert the value, like Sys_var_charptr_base::do_check_string() does.

          bar Alexander Barkov added a comment - The problem happens because Sys_var_dbug::do_check() does not convert the value to utf8. The problem is also repeatable with this script: SET collation_connection=utf16le_general_ci; SET debug_dbug= 'd,any_random_string' ; SELECT @@debug_dbug; +--------------+ | @@debug_dbug | +--------------+ | d | +--------------+ This method should fix fixed to convert the value, like Sys_var_charptr_base::do_check_string() does.

          People

            bar Alexander Barkov
            Roel Roel Van de Paar
            Votes:
            0 Vote for this issue
            Watchers:
            5 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.