To begin with, let me state that I have not either downloaded or used this product. InnoDB: A parallel scan returned an incorrect partition ID when loading data into HeatWave from a subpartitioned InnoDB table.InnoDB: An in-place DDL operation failed to flush all modified pages.InnoDB: An excessive number of notes were written to the error log when the innodb_open_files limit was temporarily exceeded.
For example, the old output Indexed full text search on t1 (which was the same in both the covering and non-covering cases) is now Full-text index search on t1 when there is no covering index, and Full-text covering index search on t1 when a covering index is used.
This fix also improves the wording used for full-text search to align with this change. Previously, this information was shown only for FORMAT=TRADITIONAL and FORMAT=JSON. For example, if idx1 is a covering index, the old output Index scan on t1 using idx1 is now shown as Covering index scan on t1 using idx1. Important Change: EXPLAIN FORMAT=TREE now shows whether an index scan uses a covering index, and thus does not need to look up other columns from the table/clustered index. For example, MySQL Enterprise Firewall and query rewrite plugins rely on query digests and existing rules for them that are associated with views may need to be updated. However, tools that use query digests may need some adjustment to account for this change. This enables distinguishing distinct SELECT statements in the events_statements_summary_by_digest table. The query digest for each SELECT statement on a view now is based on the SELECT, not the view definition. As a result, different queries had the same digest and aggregated together in the Performance Schema table events_statements_summary_by_digest, so statistics in that table were not usable for distinguishing distinct SELECT statements. Incompatible Change: For all SELECT statements on a view, the query digest was based on the view definition.
0 kommentar(er)
