[MDEV-14345] Make MariaDB stop and start ALWAYS report the version Created: 2017-11-10  Updated: 2023-10-12

Status: Open
Project: MariaDB Server
Component/s: None
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Simon Mudd Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None


 Description   

A similar feature request recently made it into MySQL: https://bugs.mysql.com/bug.php?id=87910

Motivation: I swap versions I'm using quite a lot and upgrade from one version to another so don't track in huge detail prior to stopping or starting a new version which is which. If something fails then it is very useful to know exactly which binary was being stopped (It may have been running for months so be an old version) and which is started.

If using test versions this becomes even more important.

So adding the logging:

  • as early as possible on startup
  • at the beginning and end of the shutdown phase (as sometimes the server may get stuck)
    is good to see these things and to allow you to know how or if the version has changed.

This is also good for any support people as there's a clear log and that may clarify things.

 Comments   
Comment by Simon Mudd [ 2017-11-10 ]

Hm. Priority was major. That was a mistake and if set by me was unintended. Changed to minor!

Comment by Ralf Gebhardt [ 2023-10-12 ]

I have removed the fixVersion for this task as it is one of 5.5, 10.1, 10.2, 10.3, which are EOLed.

Please add a new fixVersion if you plan to work on this task for a not EOLed versions.

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