-
Marc Alff authored
Before this fix, when starting the server without the performance schema, table performance_schema.host_cache was always empty. This is a bug: the host_cache table is populated from the actual host cache maintained by the SQL layer, and this table does not need any instrumentation active, so requiring the performance schema to be enabled is abusive. The root cause is in the table host_cache definition: the PFS_engine_table_share::m_perpetual flag was not set. With this fix, the m_perpetual flag is set for table performance_schema.host_cache, which means the table can provide data even when the performance schema is disabled. Approved by: Chris Powers <chris.powers@oracle.com>
Marc Alff authoredBefore this fix, when starting the server without the performance schema, table performance_schema.host_cache was always empty. This is a bug: the host_cache table is populated from the actual host cache maintained by the SQL layer, and this table does not need any instrumentation active, so requiring the performance schema to be enabled is abusive. The root cause is in the table host_cache definition: the PFS_engine_table_share::m_perpetual flag was not set. With this fix, the m_perpetual flag is set for table performance_schema.host_cache, which means the table can provide data even when the performance schema is disabled. Approved by: Chris Powers <chris.powers@oracle.com>
Loading