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

          Ascending order - Click to sort in descending order
          valerii Valerii Kravchuk created issue -
          valerii Valerii Kravchuk made changes -
          Field Original Value New Value
          Status Open [ 1 ] Confirmed [ 10101 ]
          elenst Elena Stepanova made changes -
          Fix Version/s 10.2 [ 14601 ]
          Priority Major [ 3 ] Minor [ 4 ]
          julien.fritsch Julien Fritsch made changes -
          Comment [ A comment with security level 'Developers' was removed. ]
          serg Sergei Golubchik made changes -
          Priority Minor [ 4 ] Major [ 3 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 10.0 [ 16000 ]
          Fix Version/s 10.1 [ 16100 ]
          serg Sergei Golubchik made changes -
          Assignee Sergei Golubchik [ serg ]
          serg Sergei Golubchik made changes -
          Sprint 10.1.29 [ 202 ]
          serg Sergei Golubchik made changes -
          Status Confirmed [ 10101 ] In Progress [ 3 ]
          serg Sergei Golubchik made changes -
          Status In Progress [ 3 ] Stalled [ 10000 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 5.5 [ 15800 ]
          serg Sergei Golubchik made changes -
          Fix Version/s 5.5 [ 15800 ]
          serg Sergei Golubchik made changes -
          Sprint 10.1.29 [ 202 ] 10.1.29, 10.1.30 [ 202, 215 ]
          serg Sergei Golubchik made changes -
          Rank Ranked higher
          serg Sergei Golubchik made changes -
          Fix Version/s 10.0.34 [ 22613 ]
          Fix Version/s 10.1.30 [ 22637 ]
          Fix Version/s 10.2.12 [ 22810 ]
          Fix Version/s 10.2 [ 14601 ]
          Fix Version/s 10.0 [ 16000 ]
          Fix Version/s 10.1 [ 16100 ]
          serg Sergei Golubchik made changes -
          Resolution Fixed [ 1 ]
          Status Stalled [ 10000 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 80133 ] MariaDB v4 [ 151870 ]
          mariadb-jira-automation Jira Automation (IT) made changes -
          Zendesk Related Tickets 127769

          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.