In my previous post (here) I talked about “InnoDB Transparent tablespace encryption” which was introduced in MySQL 5.7.11. That encryption was limited to file-per-table tablespaces. In MySQL 8.0.13, encryption for general tablespace is introduced. This blog post aims to give a peek into this new feature.…
All posts by Mayank Prasad
MySQL : InnoDB Transparent Tablespace Encryption
From MySQL 5.7.11, encryption is supported for InnoDB (file-per-table) tablespaces. This is called Transparent Tablespace Encryption or sometimes referred as Encryption at Rest. This blog post aims to give the internal details of InnoDB Tablespace Encryption.
Keyring Plugin : Why What How ?…
MySQL 8.0: Performance Schema Instrumentation of Server Errors
In MySQL 8.0.0, the Performance Schema can now instrument server errors. There are 5 new summary tables introduced:
|
1 2 3 4 5 6 7 8 9 10 11 |
mysql> show tables like "%by_error%"; +-------------------------------------------+ | Tables_in_performance_schema (%by_error%) | +-------------------------------------------+ | events_errors_summary_by_account_by_error | | events_errors_summary_by_host_by_error | | events_errors_summary_by_thread_by_error | | events_errors_summary_by_user_by_error | | events_errors_summary_global_by_error | +-------------------------------------------+ 5 rows in set (0.02 sec) |
As names suggest, statistics of errors in these tables are aggregated by error.…
New in MySQL 5.7: Performance Schema scalable memory allocation
Performance Schema is a mechanism to collect and report run time statistics for running MySQL server. These statistics are stored-in and fetched-from internal memory buffers. In MySQL 5.6 GA, memory for these buffers is allocated during MySQL server startup with either user specified configuration values or with default values that autosize.…
MySQL Statement Digests
Decoupling Statement Digests From Performance Schema
MySQL Statement Digests are a feature originally introduced as part of the MySQL Performance Schema in MySQL 5.6 to aggregate statement statistics based on the normalized statements executed within the server (for additional info, see here).…
MySQL Statement Digests: Configurable Max Lengths
MySQL Statement Digests are a feature originally introduced as part of the MySQL Performance Schema in MySQL 5.6 to aggregate statement statistics based on the normalized statements executed within the server (for additional info, see here).
Digest calculations are done based on the tokens found in the statement text.…
MySQL Performance Schema: Instrumentation Exceptions
The setup_actors table in MySQL Performance Schema can be used to specify what users and hosts one wants to have instrumentation enabled for. By default, connections from all users and hosts are instrumented:
…|
1 2 3 4 5 6 7 |
mysql> select * from performance_schema.setup_actors; +------+------+------+ | HOST | USER | ROLE | +------+------+------+ | % | % | % | +------+------+------+ 1 row in set (0.00 sec) |
You can then use standard SQL against this setup_actors table in order to specify what users and hosts you want to have instrumentation enabled for.
MySQL Performance Schema : Prepared Statements Instrumentation
MySQL 5.7.4 has a new Performance Schema feature, namely instrumentation for prepared statements. This instrumentation gives details of PREPARE and EXECUTE statistics for a prepared statement.
New Table
New table added to display run time statistics of Prepared Statements is named as prepared_statements_instances.…
Performance Schema implementation Internals: Registering instruments
This is the very first post in the series of Performance Schema Implementation Internals. This series is for MySQL Developers to understand implementation of Performance Schema. For user point of view of performance Schema, please refer to mysql documentation link : http://dev.mysql.com/doc/refman/5.7/en/performance-schema-quick-start.html
This post talks about the mechanism to register instruments in Performance Schema (referred as P_S from hereon) so that their statistics could be collected at runtime.…