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

mysqlbinlog --version output is the same on 10.x as on 5.5.x, and contains not only version

Details

    • 10.1.29, 10.1.30

    Description

      mysqlbinlog utility of MariaDB outputs it's version as 3.3, twice, no matter what real version it comes from:

      [openxs@fc23 ~]$ mysqlbinlog --version | grep mysqlbinlog
      mysqlbinlog Ver 3.3 for Linux at x86_64
      mysqlbinlog Ver 3.3 for Linux at x86_64
      Usage: mysqlbinlog [options] log-files
      The following groups are read: mysqlbinlog client client-server client-mariadb
      [openxs@fc23 ~]$ mysql --version
      mysql  Ver 15.1 Distrib 10.1.21-MariaDB, for Linux (x86_64) using readline 5.1
       
      [openxs@fc23 ~]$ dbs/maria5.5/bin/mysqlbinlog --version | grep mysqlbinlog
      dbs/maria5.5/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      dbs/maria5.5/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      Usage: dbs/maria5.5/bin/mysqlbinlog [options] log-files
      The following groups are read: mysqlbinlog client client-server client-mariadb
      [openxs@fc23 ~]$ dbs/maria5.5/bin/mysql --version
      dbs/maria5.5/bin/mysql  Ver 15.1 Distrib 5.5.54-MariaDB, for Linux (x86_64) using readline 5.1
       
      [openxs@fc23 ~]$ dbs/maria10/bin/mysqlbinlog --version | grep mysqlbinlog
      dbs/maria10/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      dbs/maria10/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      Usage: dbs/maria10/bin/mysqlbinlog [options] log-files
      The following groups are read: mysqlbinlog client client-server client-mariadb
      [openxs@fc23 ~]$ dbs/maria10/bin/mysql --version
      dbs/maria10/bin/mysql  Ver 15.1 Distrib 10.0.29-MariaDB, for Linux (x86_64) using readline 5.1
       
      [openxs@fc23 ~]$ dbs/maria10.1/bin/mysqlbinlog --version | grep mysqlbinlog
      dbs/maria10.1/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      dbs/maria10.1/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      Usage: dbs/maria10.1/bin/mysqlbinlog [options] log-files
      The following groups are read: mysqlbinlog client client-server client-mariadb
      [openxs@fc23 ~]$ dbs/maria10.1/bin/mysql --version
      dbs/maria10.1/bin/mysql  Ver 15.1 Distrib 10.1.23-MariaDB, for Linux (x86_64) using readline 5.1
       
      [openxs@fc23 ~]$ dbs/maria10.2/bin/mysqlbinlog --version | grep mysqlbinlog
      dbs/maria10.2/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      dbs/maria10.2/bin/mysqlbinlog Ver 3.3 for Linux at x86_64
      Usage: dbs/maria10.2/bin/mysqlbinlog [options] log-files
      The following groups are read: mysqlbinlog client client-server client-mariadb
      [openxs@fc23 ~]$ dbs/maria10.2/bin/mysql --version
      dbs/maria10.2/bin/mysql  Ver 15.1 Distrib 10.2.5-MariaDB, for Linux (x86_64) using readline 5.1
      

      Upstream bug report for MySQL 5.6 (https://bugs.mysql.com/bug.php?id=67643) was fixed:

      [openxs@fc23 ~]$ dbs/5.7/bin/mysqlbinlog --version
      dbs/5.7/bin/mysqlbinlog Ver 3.4 for Linux at x86_64

      I think it does make sense to increase version starting from 10.0.x, and it must be presenbted only once in the results, with no information about options etc.

      Attachments

        Activity

          Transition Time In Source Status Execution Times
          Valerii Kravchuk made transition -
          Open Confirmed
          39s 1
          Sergei Golubchik made transition -
          Confirmed In Progress
          221d 14m 1
          Sergei Golubchik made transition -
          In Progress Stalled
          10s 1
          Sergei Golubchik made transition -
          Stalled Closed
          45d 3h 59m 1

          People

            serg Sergei Golubchik
            valerii Valerii Kravchuk
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.