## ## Miscellaneous test cases for performance_schema.processlist ## ## Test cases: ## 1. Verify naming of foreground system threads. ## ## ## Test Case 1: Verify naming of foreground system threads. ## ## Foreground system threads should be named 'system user' except for ## singleton threads such as 'event_scheduler'. ## ## Reference: Bug#36895513 "Wrong result in P_S.processlist on replica node" ## NOTE: Results must be manually verified. ## # Configure two servers to be source and replica. include/master-slave.inc Warnings: Note #### Sending passwords in plain text without SSL/TLS is extremely insecure. Note #### Storing MySQL user name or password information in the connection metadata repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START REPLICA; see the 'START REPLICA Syntax' in the MySQL Manual for more information. [connection master] # Wait until the replica SQL thread has been synced and all events have been copied over to the replica. include/sync_slave_sql_with_master.inc # Stop replica. include/stop_slave.inc # Start replica. include/start_slave.inc # Verify processlist user name is 'system_user'. select * from performance_schema.processlist order by user, id; ID USER HOST DB COMMAND TIME STATE INFO EXECUTION_ENGINE event_scheduler NULL