diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-10-11 14:02:35 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2019-10-11 14:02:35 +0300 |
| commit | 4ebaf8136096a5bd383971f93f6bb0b0df83cd43 (patch) | |
| tree | b51875157e207f08b3e6e746ed7ab4eedf0f837e /mysql-test/r/sp-code.result | |
| parent | db9a4d928dc8e81ce449b54ef0bf02c248d931d4 (diff) | |
| download | mariadb-git-4ebaf8136096a5bd383971f93f6bb0b0df83cd43.tar.gz | |
MDEV-19455: Avoid SET DEBUG_DBUG='-d,...' construct
Apply the correct pattern for debug instrumentation:
SET @save_dbug=@@debug_dbug;
SET debug_dbug='+d,...';
...
SET debug_dbug=@save_dbug;
Numerous tests use statements of the form
SET debug_dbug='-d,...';
which will inadvertently enable all DBUG tracing output,
causing unnecessary waste of resources.
Diffstat (limited to 'mysql-test/r/sp-code.result')
| -rw-r--r-- | mysql-test/r/sp-code.result | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/mysql-test/r/sp-code.result b/mysql-test/r/sp-code.result index 67651294498..444b24626a7 100644 --- a/mysql-test/r/sp-code.result +++ b/mysql-test/r/sp-code.result @@ -923,6 +923,7 @@ END; CLOSE c; SELECT a INTO @foo FROM t1 LIMIT 1; # Clear warning stack END| +SET @save_dbug = @@debug_dbug; SET SESSION debug_dbug="+d,bug23032_emit_warning"; CALL p1(); Warning found! @@ -942,7 +943,7 @@ End of Result Set found! Level Code Message Warning 1105 Unknown error Error 1329 No data - zero rows fetched, selected, or processed -SET SESSION debug_dbug="-d,bug23032_emit_warning"; +SET SESSION debug_dbug=@save_dbug; DROP PROCEDURE p1; DROP TABLE t1; # |