Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inclusive Naming: replace SHOW SLAVE STATUS with SHOW REPLICA STATUS #9515

Closed
deepthi opened this issue Jan 14, 2022 · 4 comments
Closed

Inclusive Naming: replace SHOW SLAVE STATUS with SHOW REPLICA STATUS #9515

deepthi opened this issue Jan 14, 2022 · 4 comments
Assignees
Labels
Component: General Changes throughout the code base Type: Internal Cleanup

Comments

@deepthi
Copy link
Member

deepthi commented Jan 14, 2022

Once MySQL 5.7 is EOL (late 2023) and we drop support, we will be able to replace the replication commands with new ones (available in. 8.0.22+)
Unfortunately we will need to continue to use SHOW MASTER STATUS and CHANGE MASTER TO unless those have new equivalents by then.

@mattlord
Copy link
Contributor

mattlord commented Jan 16, 2022

Another alternative — that I think is clearly better, but would require a new project on our side — is to use the performance_schema replication tables instead. The master and slave terminology is already gone there.

MariaDB is significantly different here but I'm also proposing that we deprecate support for MariaDB in #9518 and the timing would align.

@mw491605
Copy link

@ajm188 ajm188 added Type: Internal Cleanup Component: General Changes throughout the code base labels Jun 21, 2022
@deepthi
Copy link
Member Author

deepthi commented Nov 15, 2022

It's not just SHOW, we also have START, RESET etc.
We should keep it simple and not bring in select from performance_schema into this path.
It occurs to me that because we already have two flavors for MySQL - 5.7 and 8.0, we can go ahead and make the changes for the 8.0 flavor now, no need to wait for 5.7 EOL. When 5.7 does EOL, we can simply delete that flavor.

@GuptaManan100 GuptaManan100 moved this to Backlog in v16.0.0 Nov 27, 2022
@frouioui frouioui added this to v17.0.0 Feb 8, 2023
@frouioui frouioui removed this from v16.0.0 Feb 8, 2023
@frouioui frouioui moved this to Backlog in v17.0.0 Feb 8, 2023
@frouioui frouioui added this to v18.0.0 Jun 30, 2023
@frouioui frouioui moved this to Backlog in v18.0.0 Jun 30, 2023
@frouioui frouioui removed this from v17.0.0 Jun 30, 2023
@GuptaManan100
Copy link
Member

GuptaManan100 commented Aug 28, 2023

We'll do this in v19.0.0 because we will drop support for MySQL 5.7 after v18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: General Changes throughout the code base Type: Internal Cleanup
Projects
Status: Done
Development

No branches or pull requests

6 participants