Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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 would be avoided by simply passing rec_printer(…).str() to the DBUG_LOG that was introduced in MDEV-11713.
Attachments
Issue Links
- relates to
-
MDEV-11649 Uninitialized field fts_token->position in innodb_fts.innodb_fts_plugin
-
- Closed
-
-
MDEV-11713 Optimize DBUG_PRINT and introduce DBUG_LOG
-
- Closed
-
f380e7b5535 MDEV-12072 Do not unnecessarily construct rec_printer objects in debug builds
For some reason,
./mtr --mysqld=--debug=d,ib_merge_sort
did not enable any output in the tests that I tried. I successfully tested this with
./mtr --mysqld=--debug=d,ib_cur