Bug #31142 mysqlbinlog --version reports the wrong version number

• Submitted: 22 Sep 2007 10:04
• Modified: 20 Jan 2017 5:40
• Reporter: Mark Callaghan
• Status: Duplicate
• Category: MySQL Server: Command-line Clients
• Severity: S4 (Feature request)
• Version: 4.0, 5.0
• OS: Any
• CPU Architecture: Any
• Tags: mysqlbinlog, version

[22 Sep 2007 10:04] Mark Callaghan

Description:
For MySQL 5.0.37:

$ mysqlbinlog -V
mysqlbinlog Ver 3.1 for unknown-linux-gnu at i686
$ mysql -V
mysql  Ver 14.12 Distrib 5.0.37, for unknown-linux-gnu (i686) using readline 5.0

And for MySQL 4.0.26:
$ mysql --version
mysql  Ver 12.22 Distrib 4.0.26, for pc-linux-gnu (i686)
$ mysqlbinlog --version
mysqlbinlog Ver 2.6 for pc-linux-gnu at i686

How to repeat:
See above

Suggested fix:
Change mysqlbinlog to report the same version number as the database

[23 Sep 2007 6:04] Valeriy Kravchuk

mysqlbinlog's version is more related to binary log format it supports than to particular server version. If you want that to be changed, this is a "feature request".

[23 Sep 2007 6:30] Mark Callaghan

I missed this the first time. The mysql binary reports its own version number and the MySQL distribution (4.0.X, 5.0.X). mysqlbinlog only reports its version number. So I want mysqlbinlog to report the MySQL distribution in addition to its version number.

This has come about from a tool that we use which confirms that the version of mysqlbinlog is from a 5.0 distribution, as it must copy from a MySQL 5.0 master and we don't want to miss any data.

[23 Sep 2007 16:59] Valeriy Kravchuk

Thank you for a reasonable feature request :)

[16 Aug 2013 19:47] Justin Swanhart

Should affect 5.1, 5.5, 5.6 and 5.7.

This is a major problem for external tools.  Please fix.

[20 Jan 2017 5:40] Erlend Dahl

Client-specific version numbers have been removed in 8.0:

Bug#55885 please remove client program versions