All Products
Search

This Product

    PolarDB:PolarDB for MySQL 5.7

    Document Center

    PolarDB:PolarDB for MySQL 5.7

    Last Updated:Apr 12, 2024

    This topic describes the updates and features of PolarDB for MySQL 5.7.

    5.7.1.0.32

    Category

    Description

    Release date

    New feature and performance optimization

    • After the global transaction identifier (GTID) feature is enabled, temporary tables can be created and deleted in transactions.

    • The Variable-Setting hint syntax is supported in the global consistency (high-performance mode) feature.

    • The performance of the thread pool is optimized when multiple threads of binary logs are concurrently written.

    2024-03-27

    Fixed issue

    • The following issue is fixed: When a child process is forked, TDE is incompatible with the RDMA memory.

    • The following issue is fixed: Subsequent scale-out requests cannot be processed after the buffer pool is scaled in because large SQL statements occupy a large number of pages for a long time.

    • The following issue is fixed: You must restart the node in case of autoinc rollback.

    • The following issue is fixed: A deadlock occurs in parallel DDL scenarios when DDL read-ahead is enabled.

    • The following issue is fixed: A new INSERT request is autoinc duplicate key after a DDL statement that modifies a partition is executed on a partition table.

    5.7.1.0.31

    Category

    Description

    Release date

    New feature and performance optimization

    The speed at which the thread pool feature processes connection requests in low-concurrency scenarios is boosted.

    2024-01-31

    Fixed issue

    • The following issue is fixed: Nodes may crash when the logical prefetching feature is used.

    • The following issue is fixed: Memory leak issues occur when you use the logical prefetching feature.

    • The following issue is fixed: When you initiate a new process for restoring individual databases and tables, the thread cannot exit due to the full disk issue.

    • The following issue is fixed: When a database or table restoration is initiated, the read-only node fails to be added because the redo log on the primary node is cleared.

    5.7.1.0.30.1

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: When autoinc_persist is enabled, autoinc rollback occurs after an HA switchover action.

    • The following issue is fixed: Autoinc rollback occurs on the primary node or read-only nodes after repeated HA switchover actions.

    • The following issue is fixed: After you perform a degrade operation on an primary node, the physical replications on the standby nodes cannot be reconnected.

    2023-12-11

    5.7.1.0.30

    Category

    Description

    Release date

    New feature and performance optimization

    • The database and table restoration feature is optimized. For example, databases and tables can be restored more quickly, and failed tasks can be rolled back.

    • The log output feature is optimized: Unnecessary error logs for the fil_space_extend function are deleted.

    2023-11-23

    Fixed issue

    • The following issue is fixed: When the physical machine of a read-only node fails, the primary node does not terminate the data replication under special circumstances. As a result, the primary node cannot flush data.

    • The following issue is fixed: Autoinc rollback caused by table cache eviction occurs due to a large number of tables after an HA switchover action.

    • The following issue is fixed: When you upgrade an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster, the migration link is interrupted due to the restart of the cluster.

    • The following issue is fixed: Abnormal checkpoints occur after an UNDO TRUNCATE statement is executed.

    • The following issue is fixed: When a read-only node is started, it is connected to the primary node not by using the polarfs dir fast scan API.

    5.7.1.0.29

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: Deadlocks occur when the cross-page logical prefetching conflicts with the merge sub-operation of a split-merge operation (SMO).

    • The following issue is fixed: The data of an InnoDB temporary table cannot be flushed.

    • The following issue is fixed: Nodes may crash if only keywords are specified but not the table schema and table name in the last rule when multiple concurrency control (CCL) rules are configured to delete the same type of SQL statements.

    2023-09-14

    5.7.1.0.28.4

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: When the page cleaner thread has a large amount of dirty data to flush but only a small percentage of the available memory can be utilized for dirty pages, the write performance of the database is compromised.

    2023-08-28

    5.7.1.0.28.2

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: When audit log is enabled, SQL latency increases due to loaded local disks.

    2023-08-02

    5.7.1.0.28

    Category

    Description

    Release date

    New feature and performance optimization

    • The innodb_polar_import_tablespace_strict_mode parameter is added. The default value is ON, which specifies that an error is returned if a database or table that you want to restore contains full-text indexes.

    • The innodb_polar_scc session-level parameter is added to specify whether to enable strong consistency for current connection requests. When the global consistency (high-performance mode) feature is enabled and the innodb_polar_scc parameter is set to true, global consistency takes effect.

    2023-07-23

    Fixed issue

    • The following issue is fixed: A standard account can delete the performance_schema database.

    • The following issue is fixed: The checkpoint LSN is not pushed down as expected.

    • The following issue is fixed: An error may be returned when you execute the ALTER TABLE ... IMPORT TABLESPACE statement on a read-write node and perform a query operation on a read-only node at the same time.

    • The following issue is fixed: When the primary node of an instance is stopped and then restarted, the secondary nodes of the instance cannot be reconnected to the primary node.

    • The following issue is fixed: When a large value is specified for the group_concat_max_len parameter, an arithmetic overflow occurs, which causes an incorrect result of the GROUP_CONCAT function.

    • The following issue is fixed: Contention for mutex locks occurs in concurrent update scenarios after PolarTrans is enabled.

    • The following issue is fixed: After the undo log reclamation mechanism is triggered on the primary node, read-only nodes crash if the nodes are connected to the database to read data.

    5.7.1.0.27.2

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: When slow query logs are concurrently recorded, a large number of SQL requests are piled up due to the abnormality of internal counter in the thread pool.

    2023-06-14

    5.7.1.0.27

    Category

    Description

    Release date

    New feature and performance optimization

    • You can record DDL and LOCK TABLE statements to the system tables.

    • The thread pool feature is compatible with CCL. After the thread pool feature is enabled and if a connection is blocked due to CCL, the connection is marked within the thread pool. The thread pool feature creates additional threads to execute the SQL statements from other connections.

    • If the index hints specified for statement outline do not exist, only an alert is reported instead of an error.

    • The show full tables from db_name like table_name syntax is optimized.

    • The Innodb_scc_timeout_count parameter is added for the global consistency (high-performance mode) feature to record the number of timeouts that occur during a query.

    • The Innodb_scc_timeout_degrade_count parameter is added for the global consistency (high-performance mode) feature to record the number of times that a query times out and is converted to an asynchronous query.

    • SQL statements are optimized to perform digest hash calculation when no outlines are available after Statement Outline is enabled.

    • The efficiency of truncating temporary tables is optimized.

    • You can query global transaction identifiers (GTIDs) only on read-only nodes.

    • The lock granularity of Polar File System (PolarFS) is optimized to significantly improve performance in some high-load scenarios.

    2023-05-08

    Fixed issue

    • The following issue is fixed: Created events cannot be deleted.

    • The following issue is fixed: A read timeout error occurs and the database cannot be connected when physical replication is established on a read-only node.

    • The following issue is fixed: The undo logs cannot be truncated.

    • The following issue is fixed: When the redo logs of a wide table is used on read-only nodes, replication latency occurs.

    5.7.1.0.26.2

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: Hot standby nodes may unexpectedly crash when the global consistency (high-performance mode) feature is enabled.

    • The following issue is fixed: PolarTrans logs cannot be reclaimed after the primary node is restarted.

    2023-03-25

    5.7.1.0.26

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: The AUTO_INCREMENT value in the CREATE TABLE statement is lost after a switchover between the primary and read-only nodes.

    • The following issue is fixed: After a cluster is started, the configurations of the innodb_buffer_pool_in_core_file parameter in the my.cnf file of the cluster do not take effect.

    • The following issue is fixed: Communication with the TDE extension is slow when large memory specifications are used.

    2023-02-27

    5.7.1.0.25

    Category

    Description

    Release date

    New feature and performance optimization

    • The semicolon (;) at the end of an SQL statement of the query parameter in the following built-in stored procedures is ignored: dbms_ccl.add_ccl_digest_rule, dbms_outln.add_index_outline, and dbms_outln.add_optimizer_outline.

    • All types of UNION clauses are supported for Statement Outline.

    • The timeout parameter related to the physical replication connection is modified to prevent issues when the physical machine where the primary node is deployed fails.

    • Thread pool optimizations:

      • You can use the thread_pool_high_priority_users parameter to configure a list of high-priority users. The thread pool preferentially allocates threads to requests from high-priority users.

      • The bypass mechanism is added. You can configure the bypass_thread_pool_ips parameter to grant special privileges to specific IP addresses. When you use the IP addresses specified in the bypass_thread_pool_ips parameter to connect to the database, the thread pool is bypassed.

      • The timeout mechanism for slow queries is added. If the thread pool counts the overall number of threads, the number of threads in the slow query state is ignored, so that the overall number of threads is not limited by the number of slow query threads.

    2023-01-06

    Fixed issue

    The following issue is fixed: The database performance may be degraded in long-running transaction scenarios.

    5.7.1.0.24

    Category

    Description

    Release date

    New feature and performance optimization

    • The Innodb_scc_timeout_count parameter is added for the global consistency (high-performance mode) feature to record the number of timeouts that occur during a query.

    • The Innodb_scc_timeout_degrade_count parameter is added for the global consistency (high-performance mode) feature to record the number of times that a query times out and is converted to an asynchronous query.

    2022-11-11

    Fixed issue

    • The following issue is fixed: The physical replication module on the primary node occupies additional memory.

    • The following issue is fixed: Undo logs cannot be cleared in special scenarios.

    • The following issue is fixed to improve system stability in high-concurrency scenarios: Keepalive check control fails in special scenarios.

    5.7.1.0.23.3

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: Read-only nodes crash when the hash values of file names conflict.

    2022-09-17

    5.7.1.0.23

    Category

    Description

    Release date

    New feature and performance optimization

    • The global consistency (high-performance mode) feature is added. After the global consistency (high-performance mode) feature is enabled for a PolarDB cluster, read-only nodes in the cluster provide strong consistency for read operations. For more information, see Overview.

    • The read-ahead mechanism for DDL statements is optimized to improve the efficiency of creating indexes.

    • Optimized DDL sorting: Two-way merging is changed to multiple-way merging to reduce I/O operations and improve the performance of creating indexes by executing DDL statements.

    • The high concurrency performance of the thread pool is enhanced.

    2022-08-30

    Fixed issue

    The following issue is fixed: Slow logs are not recorded when a database is deleted.

    5.7.1.0.22

    Category

    Description

    Release date

    New feature and performance optimization

    The read-ahead mechanism for DDL statements is supported, which improves the efficiency of index creation.

    2022-06-17

    Fixed issue

    • When the optimizer selects indexes that can accelerate the execution of ORDER BY clauses, it takes the costs for obtaining data from tables into consideration.

    • The following issue is fixed: When a large number of dirty pages exist in the buffer pool and page buffer pool flushing is slow, the least used page cannot be evicted.

    5.7.1.0.21

    Category

    Description

    Release date

    New feature and performance optimization

    The latency of physical replication between primary and secondary nodes is reduced to milliseconds.

    2022-05-20

    Fixed issue

    • The issue that causes high latency when physical replication is performed during a time period of low workloads in the cluster is fixed.

    • The process for selecting indexes is improved. Indexes that can provide ordering information to accelerate the execution of ORDER BY clauses are prioritized.

    • The following issue is fixed: The optimizer fails to choose a better path to the range of an index for some GROUP BY statements.

    • The following issue is fixed: When the primary node establishes a replication relationship with read-only nodes, the primary node fails to immediately apply the checkpoint policy.

    5.7.1.0.20

    Category

    Description

    Release date

    New feature and performance optimization

    During SQL parsing, OF, COMMIT_ON_SUCCESS, ROLLBACK_ON_FAIL, and TARGET_AFFECT_ROW are changed from reserved keywords to non-reserved keywords.

    2022-04-07

    5.7.1.0.17

    Category

    Description

    Release date

    New feature and performance optimization

    • The hot row optimization feature is supported. For more information, see Hot row optimization.

    • The hot standby node feature is supported to further optimize high availability efficiency.

    2022-01-14

    5.7.1.0.16

    Category

    Description

    Release date

    Fixed issue

    The policy of manually triggering checkpoints is optimized.

    2021-12-14

    5.7.1.0.15

    Category

    Description

    Release date

    New feature and performance optimization

    The fast query cache feature is added. For more information, see Fast query cache.

    2021-11-17

    5.7.1.0.14

    Category

    Description

    Release date

    Fixed issue

    • Optimizer hints are provided for users to determine whether to force merge views. For more information, see MySQL official document.

    • The SELECT FOR UPDATE WAIT N syntax is supported. N specifies the number of seconds during which a row remains locked. The timeout applies only to locking a single row. To lock multiple rows for a query, the system detects the timeout only based on a single row instead of multiple rows. If the lockout time exceeds the specified N value, the system returns the following error message: Lock wait timeout exceeded; try restarting transaction.

    2021-10-19

    5.7.1.0.13

    Category

    Description

    Release date

    New feature and performance optimization

    A read-only node of a secondary cluster in a global database network (GDN) can be promoted to be the primary node by running the alter polar to slave command. This implements the high availability of clusters.

    2021-09-10

    5.7.1.0.12

    Category

    Description

    Release date

    New feature and performance optimization

    2021-08-27

    Fixed issue

    • The statement concurrency control rules where databases and tables are specified cannot match actual conditions.

    • The process of loading redo logs is accelerated for the read-only nodes and the secondary cluster, which improves the synchronization efficiency of the primary node.

    5.7.1.0.11

    Category

    Description

    Release date

    New feature and performance optimization

    The polar_replica_work_on_nonblock_mdl_mode parameter is added. If this parameter is set to on, the uncommitted transactions that use the READ UNCOMMITTED or READ COMMITTED isolation level on read-only nodes no longer block DDL operations on the primary node. In addition, atomicity, consistency, isolation, and durability (ACID) is no longer ensured for the operations of creating tables on the read-only nodes.

    2021-07-08

    5.7.1.0.10

    Category

    Description

    Release date

    New feature and performance optimization

    This version is compatible with MySQL 8.0 and supports the SELECT FOR UPDATE, SHARE SKIP LOCKED, and NOWAIT statements. For more information, see MySQL 8.0.

    2021-06-15

    Fixed issue

    Data in temporary tables in InnoDB databases can be saved to disks by using read-only nodes.

    5.7.1.0.9

    Category

    Description

    Release date

    Fixed issue

    • When data is retrieved from multiple tables, the storage engine can be quickly launched.

    • The following issue is fixed: The database crashes when you roll back an update operation on a virtual column.

    2021-05-13

    5.7.1.0.8

    Category

    Description

    Release date

    New feature and performance optimization

    A feature is added to decide whether the primary node must apply the checkpoint policy immediately when it establishes a replication relationship with read-only nodes.

    2021-04-19

    Fixed issue

    • KICKOUT is used as a non-reserved keyword.

    • The following issue is fixed: The encryption information in tables that are encrypted by TDE may be lost during a failover. This results in decryption errors.

    5.7.1.0.7

    Category

    Description

    Release date

    New feature and performance optimization

    • The parallel DDL feature is supported. This feature accelerates the execution of DDL statements. For more information, see Parallel DDL.

    • The innodb_buffer_pool_in_core_file parameter is added. This way, buffer pools can be removed from core files.

    • The following index hints are supported. This allows the optimizer to use or ignore the specified indexes when the optimizer processes queries.

      • GROUP_INDEX or NO_GROUP_INDEX: The system uses or ignores the specified indexes for an index scan that contains GROUP BY operations.

      • INDEX or NO_INDEX: The system forces the server to use or ignore the specified indexes.

      • JOIN_INDEX or NO_JOIN_INDEX: The system forces MySQL to use or ignore the specified indexes regardless of what method is used to query data.

    • The following join order hints are supported. This allows the optimizer to join tables in a valid order.

      • JOIN_FIXED_ORDER: The system forces the optimizer to join tables by using the order in which the tables appear in the FROM clause.

      • JOIN_ORDER: The optimizer is configured to join tables by using the specified order. This hint applies to named tables. The optimizer may place tables that are not named anywhere in the join order, including between specified tables.

      • JOIN_PREFIX: The optimizer is configured to join the first several tables in the join plan by using the specified order. This hint applies to named tables. The optimizer places all other tables after named tables.

      • JOIN_SUFFIX: The optimizer is configured to join the last several tables in the join plan by using the specified order. This hint applies to named tables. The optimizer places all other tables before named tables.

    2021-03-10

    Fixed issue

    • The mapping of token numbers is rearranged and some tokens are reserved. This fixes the issue that the digest hash value of a statement is changed after a new token is inserted.

    • The following issue is fixed: A configuration update may fail because read-only nodes cannot be registered on the primary node.

    • The following issue is fixed: A cluster abnormally exits due to the creation or deletion of temporary tables during a stored procedure after the session_track_temporary_tables system variable is enabled.

    5.7.1.0.6.3

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: The SHOW PROCESSLIST statement in some scenarios returns an invalid result.

    2021-02-22

    5.7.1.0.6.2

    Category

    Description

    Release date

    Fixed issue

    The following issue is fixed: The 1032 error code and the Can't find record in TABLE error message are reported when you perform a query that is optimized by Index Merge on a read-only node.

    2021-02-10

    5.7.1.0.6.1

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: Dirty page flushing cannot be performed as expected on read/write nodes.

    • The following issue is fixed: The primary zone cannot be changed for a cluster that has performed a failover.

    • The following issue is fixed: The database crashes if Thread Descriptor (THD) is invoked when the SHOW PROCESSLIST statement is being executed.

    2021-02-02

    5.7.1.0.6

    Category

    Description

    Release date

    New feature and performance optimization

    • The Statement Queue feature is added. For more information, see Statement queue.

    • The Instant ADD COLUMN feature is supported. This feature can instantly add columns to a table. For more information, see Instant ADD COLUMN.

    • The Returning feature is added. For more information, see Returning.

    • The default value of the innodb_adaptive_hash_index parameter is changed from ON to OFF.

    2021-01-29

    Fixed issue

    The following issue is fixed: The system tables of a PolarDB cluster are lost when the engine version of the cluster is upgraded.

    5.7.1.0.5

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: Read-only nodes crash when you query data from the read-only nodes after the key of the primary node is modified.

    • The following issue is fixed: Read-only nodes crash when you analyze partitioned tables on the read-only nodes.

    • The following issue is fixed: The new primary node crashes due to tablespace inconsistency after a failover is performed.

    2020-12-31

    5.7.1.0.4

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: Data cannot be inserted into temporary tables after a failover is performed.

    • The following issue is fixed: A read-only node becomes unavailable when a temporary tablespace is extended on the read-only node.

    • The following issue is fixed: The simulated AIO does not work as expected.

    2020-11-17

    5.7.1.0.3

    Category

    Description

    Release date

    New feature and performance optimization

    Transparent data encryption (TDE) is supported.

    2020-10-21

    Fixed issue

    • The following issue is fixed: Statistics are inconsistent between the primary node and read-only nodes.

    • The following issue is fixed: An error is returned after you execute the SHOW PROCESSLIST statement.

    5.7.1.0.2

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: IDB files cannot be created after a migration from ApsaraDB RDS for MySQL 5.7.

    • You cannot run CF_STATUS_COMMAND commands during a failover process. This is to ensure that the failover process succeeds.

    • The following issue is fixed: The primary node becomes unavailable due to page contention that is caused by updating the aggregation thread and the truncate logic in the background.

    2020-08-28

    5.7.1.0.1

    Category

    Description

    Release date

    Fixed issue

    • The following issue is fixed: MaxScale becomes inaccessible due to the missing code of some exclusive commands in PolarDB.

    • The following issue is fixed: The cluster that is restored from the cluster recycle bin is unavailable because no tablespaces are found.

    • The following issue is fixed: The unmount PFS error occurs if one or more files are still open when you run the promote replica command.

    2020-07-30