diff options
author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-02-16 09:16:11 +0200 |
---|---|---|
committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-02-16 09:16:11 +0200 |
commit | 7a5288015c8afeaaef4d5dd04057f78c7978eeee (patch) | |
tree | 107120e3de276204b25412f0cf7b2c9002173632 /mysql-test | |
parent | 37925c6ccc61bd4d5af4956dbd877c69983c09f3 (diff) | |
download | mariadb-git-7a5288015c8afeaaef4d5dd04057f78c7978eeee.tar.gz |
MDEV-12072 Do not unnecessarily construct rec_printer objects
I introduced the rec_printer object in MySQL to pretty-print raw InnoDB
records and index tuples in diagnostic messages. These objects are being
constructed unconditionally, even though the DBUG_PRINT is not enabled.
The unnecessary work is avoided by simply passing rec_printer(…).str()
to the DBUG_LOG macro that was introduced in MDEV-11713.
Diffstat (limited to 'mysql-test')
0 files changed, 0 insertions, 0 deletions