PDF (A4) - 41.9Mb
Man Pages (TGZ) - 272.4Kb
Man Pages (Zip) - 378.2Kb
Info (Gzip) - 4.2Mb
Info (Zip) - 4.2Mb
Before using thesys schema, the prerequisites described in this section must be satisfied.
Because thesys schema provides an alternative means of accessing the Performance Schema, the Performance Schema must be enabled for thesys schema to work. SeeSection 29.3, “Performance Schema Startup Configuration”.
For full access to thesys schema, a user must have these privileges:
INSERTandUPDATEfor thesys_configtable, if changes are to be made to itAdditional privileges for certain
sysschema stored procedures and functions, as noted in their descriptions (for example, theps_setup_save()procedure)
It is also necessary to have privileges for the objects underlying thesys schema objects:
Certain Performance Schema instruments and consumers must be enabled and (for instruments) timed to take full advantage ofsys schema capabilities:
All
waitinstrumentsAll
stageinstrumentsAll
statementinstrumentsandxxx_currentconsumers for all eventsxxx_history_long
You can use thesys schema itself to enable all of the additional instruments and consumers:
CALL sys.ps_setup_enable_instrument('wait');CALL sys.ps_setup_enable_instrument('stage');CALL sys.ps_setup_enable_instrument('statement');CALL sys.ps_setup_enable_consumer('current');CALL sys.ps_setup_enable_consumer('history_long'); For many uses of thesys schema, the default Performance Schema is sufficient for data collection. Enabling all the instruments and consumers just mentioned has a performance impact, so it is preferable to enable only the additional configuration you need. Also, remember that if you enable additional configuration, you can easily restore the default configuration like this:
CALL sys.ps_setup_reset_to_default(TRUE);PDF (A4) - 41.9Mb
Man Pages (TGZ) - 272.4Kb
Man Pages (Zip) - 378.2Kb
Info (Gzip) - 4.2Mb
Info (Zip) - 4.2Mb