[#MDEV-20359] mysqlbinlog --version doesn't print associated MariaDB version

[MDEV-20359] mysqlbinlog --version doesn't print associated MariaDB version Created: 2019-08-15 Updated: 2023-04-27
Status:	Open
Project:	MariaDB Server
Component/s:	Replication, Scripts & Clients
Affects Version/s:	10.2.26, 10.1.41, 10.3.17, 10.4.7
Fix Version/s:	10.4

Type:

Bug

Priority:

Major

Reporter:

Geoff Montee (Inactive)

Assignee:

Andrei Elkin

Resolution:

Unresolved

Votes:

Labels:

None

Description

Most client tools print the associated MariaDB version when the --version option is provided to the tool. For example:

[ec2-user@ip-172-30-0-58 ~]$ mysql --version

mysql  Ver 15.1 Distrib 10.2.26-MariaDB, for Linux (x86_64) using readline 5.1

[ec2-user@ip-172-30-0-58 ~]$ mysqladmin --version

mysqladmin  Ver 9.1 Distrib 10.2.26-MariaDB, for Linux on x86_64

[ec2-user@ip-172-30-0-58 ~]$ mysqldump --version

mysqldump  Ver 10.16 Distrib 10.2.26-MariaDB, for Linux (x86_64)

However, mysqlbinlog doesn't currently do that:

[ec2-user@ip-172-30-0-58 ~]$ mysqlbinlog --version

mysqlbinlog Ver 3.3 for Linux at x86_64

If we compare the relevant code for mysqlbinlog to the code for mysql, then we can see why:

I think mysqlbinlog should print a more complete version string, like the other client tools.

Generated at Thu Feb 08 08:58:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.