Details
-
Task
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
A US-based user has asked me whether we can rename or alias slave-related statements, options, status variables. I believe that discussions involving slaves can be uncomfortable for some people due to the history of slavery in the U.S.
I have no idea how prevalent this feeling is, but I do know that several other software teams have done similar changes recently. For example:
https://www.theregister.co.uk/2018/09/11/python_purges_master_and_slave_in_political_pogrom/
https://www.theregister.co.uk/2018/09/13/redis_master_slave/
https://github.com/antirez/redis/issues/5335
https://github.com/kubernetes/website/issues/6525
https://www.drupal.org/node/2275877 - replica
If we did want to do this, then some potential replacements are:
- replica
- clone
- replicator
- standby
- secondary
- follower
Attachments
Issue Links
- includes
-
MDEV-20601 Make REPLICA a synonym for SLAVE in SQL statements
-
- Closed
-
-
MDEV-20602 Make REPLICA a synonym for SLAVE for sysvars
-
- Open
-
-
MDEV-20603 Make REPLICA a synonym for SLAVE for status vars
-
- Open
-
-
MDEV-29248 Description of master_verify_checksum mentions "slave"
-
- Open
-
- is blocked by
-
MDEV-19855 Create "Sql_cmd_show_slave_status" class for "SHOW SLAVE STATUS" command.
-
- Closed
-
- is duplicated by
-
MDEV-18264 Rename Master/Slave
-
- Closed
-
-
MDEV-30273 Replace inappropriate naming (slave,master) with appropriate one (replica,source)
-
- Closed
-
- relates to
-
MDEV-24362 Privilege aliases are missing from SHOW PRIVILEGES
-
- Open
-