MySQL 8.0.30
Source Code Documentation
Opt_trace_info Struct Reference

User-visible information about a trace. More...

#include <opt_trace.h>

Public Attributes

const char * trace_ptr
 String containing trace. More...
 
size_t trace_length
 length of trace string / String containing original query. 0-termination: like trace_ptr. More...
 
const char * query_ptr
 
size_t query_length
 length of query string More...
 
const CHARSET_INFOquery_charset
 charset of query string More...
 
size_t missing_bytes
 How many bytes this trace is missing (for traces which were truncated because of @@optimizer-trace-max-mem-size). More...
 
bool missing_priv
 whether user lacks privilege to see this trace More...
 

Detailed Description

User-visible information about a trace.

See also
Opt_trace_iterator.

Member Data Documentation

◆ missing_bytes

size_t Opt_trace_info::missing_bytes

How many bytes this trace is missing (for traces which were truncated because of @@optimizer-trace-max-mem-size).

◆ missing_priv

bool Opt_trace_info::missing_priv

whether user lacks privilege to see this trace

◆ query_charset

const CHARSET_INFO* Opt_trace_info::query_charset

charset of query string

◆ query_length

size_t Opt_trace_info::query_length

length of query string

◆ query_ptr

const char* Opt_trace_info::query_ptr

◆ trace_length

size_t Opt_trace_info::trace_length

length of trace string / String containing original query. 0-termination: like trace_ptr.

◆ trace_ptr

const char* Opt_trace_info::trace_ptr

String containing trace.

If trace has been end()ed, this is 0-terminated, which is only to aid debugging or unit testing; this property is not relied upon in normal server usage. If trace has not been ended, this is not 0-terminated. That rare case can happen when a substatement reads OPTIMIZER_TRACE (at that stage, the top statement is still executing so its trace is not ended yet, but may still be read by the sub-statement).


The documentation for this struct was generated from the following file: