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

Outdated VARIABLE_COMMENT for HISTOGRAM_TYPE in I_S.SYSTEM_VARIABLES and help

    XMLWordPrintable

Details

    Description

      *************************** 1. row ***************************
              VARIABLE_NAME: HISTOGRAM_TYPE
              SESSION_VALUE: DOUBLE_PREC_HB
               GLOBAL_VALUE: DOUBLE_PREC_HB
        GLOBAL_VALUE_ORIGIN: COMPILE-TIME
              DEFAULT_VALUE: DOUBLE_PREC_HB
             VARIABLE_SCOPE: SESSION
              VARIABLE_TYPE: ENUM
           VARIABLE_COMMENT: Specifies type of the histograms created by ANALYZE. Possible values are: SINGLE_PREC_HB - single precision height-balanced, DOUBLE_PREC_HB - double precision height-balanced.
          NUMERIC_MIN_VALUE: NULL
          NUMERIC_MAX_VALUE: NULL
         NUMERIC_BLOCK_SIZE: NULL
            ENUM_VALUE_LIST: SINGLE_PREC_HB,DOUBLE_PREC_HB,JSON_HB
                  READ_ONLY: NO
      COMMAND_LINE_ARGUMENT: REQUIRED
          GLOBAL_VALUE_PATH: NULL
      1 row in set (0.003 sec)
      

      $ sql/mysqld --help --verbose
      <...>
        --histogram-type=name 
                            Specifies type of the histograms created by ANALYZE.
                            Possible values are: SINGLE_PREC_HB - single precision
                            height-balanced, DOUBLE_PREC_HB - double precision
                            height-balanced.
      

      The new JSON_HB value is missing from VARIABLE_COMMENT and help text.

      Attachments

        Issue Links

          Activity

            People

              psergei Sergei Petrunia
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.