[MDEV-9593] Print the real version in the error log Created: 2016-02-19  Updated: 2022-10-26  Resolved: 2016-09-01

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: 10.2
Fix Version/s: 10.2.2

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergey Vojtovich
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-20344 startup messages belong in stderr/err... Closed
Relates
relates to MDEV-10967 Print the real version in the error l... Closed
relates to MDEV-6873 On startup please make MariaDB report... Closed
relates to MDEV-7780 Support for faking server version Closed
relates to MDEV-10648 mysqld --log-error prints on stdout a... Confirmed
relates to MDEV-20287 Have the server process print a "star... Open
relates to MDEV-20344 startup messages belong in stderr/err... Closed
relates to MDEV-21046 Print server version to error log ins... Open
relates to MDEV-21711 Log: "Server Version xx.xx.xx startin... Open
Sprint: 10.2.0-6, 10.2.0-7, 10.2.2-2

 Description   

It's related to MDEV-7780 where @@version has become writable.

I don't know if it's technically possible, but if it is, it would be extremely useful to additionally print the real version (one returned by mysqld --version without an argument) in the error log upon startup and, better still, also upon a crash. We are going to have major problem with users setting this variable, because they will set it in the config file, will never update it in a timely manner (naturally, because they can get upgrades automatically), and we won't know which real version they report their problem against, finding it out will require additional negotiations and won't always be successful.



 Comments   
Comment by Sergey Vojtovich [ 2016-03-10 ]

We should also fix the problem mentioned in the following commit by using real version:
https://github.com/MariaDB/server/commit/70a4856df8c2af14e2d0a32b8d49bbd2bd2fc464

Comment by Sergey Vojtovich [ 2016-08-26 ]

serg, please review fix for this bug.

Comment by Sergey Vojtovich [ 2016-08-26 ]

serg, this task was supposed to be in this current sprint. Not sure why it wasn't added.

Generated at Thu Feb 08 07:35:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.