Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-23610

Slave user can't run "SHOW SLAVE STATUS" anymore after upgrade to 10.5, mysql_upgrade should take of that

Details

    Description

      A user that had REPLICATION SLAVE, REPLICATION CLIENT privileges before upgrade to 10.5, has REPLICATION SLAVE, BINLOG MONITOR after upgrade, but is not able to run SHOW SLAVE STATUS anymore, as it is missing the new REPLICATION SLAVE ADMIN privilege now which is necessary for this in 10.5.

      IMHO mysql_upgrade should take care of replacing REPLICATION CLIENT with BINLOG MONITOR, REPLICATION SLAVE ADMIN when doing a pre-10.5 to 10.5 or later upgrade.

      Same for REPLICATION SLAVE, that should become REPLICATION SLAVE, REPLICATION MASTER ADMIN, REPLICATION SLAVE ADMIN instead on upgrades to 10.5., so that existing users can still continue to use SHOW SLAVE HOSTS and SHOW RELAYLOG EVENTS.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Sujatha Sivakumar (Inactive) made transition -
            Open Confirmed
            70d 21h 29m 1
            Sujatha Sivakumar (Inactive) made transition -
            Confirmed In Progress
            4s 1
            Sujatha Sivakumar (Inactive) made transition -
            In Progress In Review
            4d 23h 3m 1
            Sergei Golubchik made transition -
            In Review Stalled
            1d 28m 1
            Sujatha Sivakumar (Inactive) made transition -
            Stalled Closed
            3d 18h 56m 1

            People

              sujatha.sivakumar Sujatha Sivakumar (Inactive)
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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