[MDEV-22483] mysql_upgrade does not use current user as default for connecting to server - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Minor
Resolution: Fixed
Affects Version/s: 10.5, 5.5(EOL), 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
Fix Version/s: 10.5.4, 10.2.33, 10.3.24, 10.4.14
Component/s: Scripts & Clients
Labels:
None

Description

mysql_upgrade promises to use the current user to connect to the server unless it was specified in options, but it doesn't happen, it actually has root as a hardcoded default:

10.5 f544a712
$ bin/mysql_upgrade --help \| grep user
-u, --user=name User for login if not current user.
user root

Apparently it has always be so, didn't matter much. It may be a bit more important after switching to unix_socket authentication in 10.4+, because the current user may well have a super-user account in the database. Still, if we want to change it, it is probably only safe to do in 10.5+. Alternatively, we can claim it is by design and just change the help text (which should then be done in all versions where it doesn't work).

Attachments

Issue Links

relates to

MDEV-22485 mysqlslap does not use current user as default for connecting to server

Closed

MDEV-22484 mariabackup does not use current user as default for connecting to server

Open

MDEV-24904 mariadb-upgrade does not consider O/S user as other utilities

Open

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2020-05-06 17:19

Updated:: 2021-03-28 16:47

Resolved:: 2020-05-08 12:29

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.