Bug #21970806 - SYSSCHEMA.FN_PS_THREAD_TRX_INFO UNSTABLE ON PB2

Author: MarkLeith

mysql-test/suite/sysschema/r/fn_ps_thread_trx_info.result

@@ -80,7 +80,7 @@ JSON_CONTAINS(@json_doc, '"COMMIT"', '$[0].statements_executed[1].sql_text')
 SET @sys.ps_thread_trx_info.max_length = 100;
 SELECT sys.ps_thread_trx_info(@ps_thread_id);
 sys.ps_thread_trx_info(@ps_thread_id)
-{ "error": "Trx info truncated: Row 12 was cut by GROUP_CONCAT()" }
+{ "error": "Trx info truncated: Row 1X was cut by GROUP_CONCAT()" }
 SET @sys.ps_thread_trx_info.max_length = NULL;
 SELECT JSON_VALID(sys.ps_thread_trx_info(@ps_thread_id));
 JSON_VALID(sys.ps_thread_trx_info(@ps_thread_id))

mysql-test/suite/sysschema/t/fn_ps_thread_trx_info.test

@@ -78,6 +78,7 @@ SELECT JSON_CONTAINS(@json_doc, '"COMMIT"', '$[0].statements_executed[1].sql_tex
 SET @sys.ps_thread_trx_info.max_length = 100;
 
 # Should return an error JSON object
+--replace_regex /Row 1[1-2] was/Row 1X was/
 SELECT sys.ps_thread_trx_info(@ps_thread_id);
 
 # Setting the user variable back to NULL should reset to 65535 from sys_config, and no truncation