This topic describes the release notes for PolarDB and provides links to the relevant references.
February 2024
Feature | Description | Release date | References |
Migration assessment | The migration assessment feature is provided by PolarDB to ensure the successful execution of migration tasks and high migration efficiency. This feature allows you to pre-verify the prerequisites such as the instance status, migration task dependencies, and attributes of the source instance before you upgrade an ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster. This way, you can identify the factors that may affect the migration progress and resolve the issue in advance to reduce the processing and resource costs during migration. | 2024-2-21 | |
Upgrade assessment | The upgrade assessment feature is provided by PolarDB for major version upgrades to ensure the successful execution of upgrade links and high upgrade efficiency. This feature allows you to pre-verify the prerequisites such as the cluster status, upgrade task dependencies, and attributes of the source cluster before you perform a major version upgrade. This way, you can identify the factors that may affect the upgrade progress and resolve the issue in advance to reduce the processing and resource costs during upgrade. | 2024-2-21 | |
PolarProxy configurations | The On-demand Connection option is added to the SLB Settings configuration item of PolarProxy configurations. Note This option is available only when the Load Balancing Policy option is set to Active Request-based Load Balancing. | 2024-02-22 | |
Upgrade from an ApsaraDB RDS for MySQL instance that uses X-Engine to a PolarDB for MySQL cluster | An ApsaraDB RDS for MySQL instance that uses X-Engine can be upgraded to a PolarDB for MySQL cluster. | 2024-02-29 | Upgrade an ApsaraDB RDS for MySQL instance that uses X-Engine to a PolarDB for MySQL cluster |
January 2024
Feature | Description | Release date | References |
Behavior of encryption rules configured by using RAM permission control | In PolarDB for MySQL, policies can be configured for database administrators (DBAs) and developers in the RAM console to restrict their changes to encryption rules. | 2024-01-08 | Configure the behavior of encryption rules by using RAM permission control |
PolarProxy configurations | The Column store nodes handle OLTP requests option is added to the HTAP Optimization configuration item of PolarDB for MySQL cluster endpoints. | 2024-01-15 |
December 2023
Feature | Description | Release date | References |
Description change of retention period in backup and restoration policies | Phrases related to permanent retention in documentations are changed to long-term retention. | 2023-12-26 | |
Weight-based load balancing | Endpoint-level weight can be configured for each node in a cluster endpoint or a custom endpoint in PolarDB for MySQL. The endpoint-level weight takes precedence over the global weight configured based on databases. | 2023-12-28 |
November 2023
Feature | Description | Release date | References |
Download of backup files | The backup files of a cluster backup set in the CSV, SQL, or Parquet format can be downloaded to your on-premises computer for other purposes. Sample purposes:
| November 24 Note This feature is in canary release and will be formally launched later. | |
IMCI-based multi-node MPP | Multi-node massively parallel processing (MPP) based on In-Memory Column Index (IMCI) is supported. IMCI-based multi-node MPP is a multi-node execution group that consists of multiple read-only column store nodes and implements the multi-node parallel execution of queries. IMCI-based multi-node MPP is suitable for the following scenarios:
| November 6 | |
Manual switchover of secondary zones | The secondary zone of a cluster can be manually changed. | November 1 |
October 2023
Feature | Description | Release date | References |
Database and table restoration performed on 50,000 tables in PolarDB clusters | Database and table restoration can be performed on more than 50,000 tables including system tables in PolarDB clusters. | October 19 | Method 1 for database and table restoration: Restore from a backup set Method 2 for database and table restoration: Restore data to an earlier point in time |
Online switchover of the VPC and vSwitch of a PolarDB cluster | The virtual private cloud (VPC) and vSwitch of the primary endpoint, cluster endpoint, and custom endpoint can be changed in PolarDB for MySQL Enterprise Edition. This feature can be used to migrate the endpoint of a PolarDB cluster to another VPC or vSwitch. | October 17 |
September 2023
Feature | Description | Release date | References |
AATs available for joining AI models and tables in PolarDB | PolarDB for AI augmented tables (AATs) that contain AI model inference columns in databases can be generated by PolarDB for AI. Data tables enhanced by AI can be used in scenarios where data and AI converge to help you perform data insight and adjust decisions based on actual conditions. | September 26 | Write the AI model-based inference results back to a database |
Integration of Tongyi Qianwen-7b (Qwen-7B) with PolarDB for AI | As a built-in model of the PolarDB, Qwen-7B is integrated with PolarDB for AI and suitable for various scenarios such as sentiment analysis, positive or negative evaluation, summary, translation, and dialogue. | September 21 | Use the Tongyi Qianwen model for data inference and interaction |
Serverless feature for column store nodes | The serverless feature can be enabled for read-only column store nodes in PolarDB for MySQL. You can configure the scaling range of resources for a read-only column store node with defined specifications to temporarily scale resources on demand. You can also create a read-only column store node without defined specifications. The specifications of the node are scaled based on your business loads to reduce costs. | September 20 |
August 2023
Feature | Description | Release date | References |
Intelligent stress testing for major version upgrades | The intelligent stress testing feature is provided by Database Autonomy Service (DAS). Before a major version upgrade, you can use the feature to simulate your business traffic running in a PolarDB cluster of a specified version. This helps you achieve the following goals:
| 2023-08-31 | |
New offset items for storage plans | Storage plans can be used to offset fees for the storage usage of level-2 backups, log backups, cold data, and PL0 ESSDs. In addition, some offset factors are adjusted. | 2023-08-17 |
July 2023
Feature | Description | Release date | References |
Price reduction for SQL Explorer and Audit | The new version of the SQL Explorer and Audit feature is supported. The new version of the SQL Explorer and Audit feature uses a different storage architecture that separates hot data from cold data. This reduces the cost of using the feature by 17% to 83%. | 2023-07-24 |
June 2023
Feature | Description | Release date | References |
New method used to enable binary logging | A new method is provided to enable binary logging. You can click Enable binary logging on the Basic Information page of a cluster to enable binary logging for the cluster. | 2023-06-09 |
April 2023
Feature | Description | Release date | References |
Serverless clusters with defined specifications | Serverless clusters with defined specifications are supported. You can enable the serverless feature for an existing common cluster with defined specifications to create a serverless cluster with defined specifications. | 2023-04-14 | Enable the serverless feature for a common cluster with defined specifications |
March 2023
Feature | Description | Release date | References |
Version management enhanced | A PolarDB for MySQL cluster can be upgraded from an earlier version to a later version. | 2023-03-31 | |
Cold data archiving | Cold data can be archived to OSS to reduce data storage costs in PolarDB for MySQL. You can archive cold data in the CSV or ORC format. You can also create a data lifecycle management (DLM) policy on a primary node to automatically archive cold data. For more information, see Archive cold data and Usage. | 2023-03-01 |
February 2023
Feature | Description | Release date | References |
X-Engine Edition | X-Engine can be enabled for a purchased PolarDB MySQL cluster. In addition, the ALTER statement can be executed to switch the storage engine of tables from InnoDB to X-Engine. The hybrid deployment of InnoDB and X-Engine can compress and store cold data of the cluster and dump the data to X-Engine without affecting the use of the InnoDB engine. This reduces storage costs by 70%. | 2023-02-06 |
January 2023
Feature | Description | Release date | References |
DBS for logical backup | Logical backup by using Database Backup (DBS) is supported for PolarDB for MySQL. | 2023-01-31 | |
PolarDB for AI | PolarDB for AI is an in-database distributed machine learning component based on PolarDB for MySQL. PolarDB for AI adopts the cloud-native architecture and provides a series of MLOps that support machine learning by using SQL statements. These MLOps include creating models, training models, viewing model status, viewing model lists, and performing model-based reasoning. PolarDB for AI also provides multiple built-in algorithms for machine learning and artificial intelligence: classification algorithms, regression algorithms, and clustering algorithms. | 2023-01-10 | |
Connection diagnostics | The connection diagnostics feature of PolarDB for MySQL can be used to check whether an Elastic Compute Service (ECS) instance or an IP address can access databases. | 2023-01-10 |
December 2022
Feature | Description | Release date | References |
Advanced monitoring | The advanced monitoring feature is provided by PolarDB for MySQL. This feature supports a wide range of performance metrics and custom charts, and provides powerful diagnostic capabilities. This feature can detect events on clusters in a timely manner and perform diagnostics on the events. This feature also provides root cause analysis and suggestions. You also have the option to manually select time periods for diagnostic analysis. | 2022-12-29 | |
Performance insight (new) | The diagnostics feature that integrates specific features of DAS is provided by PolarDB for MySQL. You can use the performance insight (new) feature to aggregate the statistics on SQL statements, rapidly evaluate workloads on your cluster, identify the root causes of performance issues, and seek appropriate solutions. This helps you improve the stability of your cluster. | 2022-12-26 | |
Serverless clusters | Serverless clusters are supported. Serverless clusters provide real-time scalability for CPU, memory, storage, and network resources and contribute to a new form of PolarDB for MySQL that uses a storage-compute separation architecture. | 2022-12-23 |
November 2022
Feature | Description | Release date | References |
Cluster lock feature | The cluster lock feature can be enabled to prevent potential irreversible consequences arising from accidental manual release of clusters. | 2022-11-20 |
September 2022
Feature | Description | Release date | References |
Global IP whitelist | Custom IP whitelist templates can be configured and associated with a cluster. You need to only configure one set of IP whitelist templates for all associated clusters. | 2022-09-26 |
June 2022
Feature | Description | Release date | References |
PolarStore Level 4 (PSL4) | PSL4 is supported. As a new storage type for PolarDB, PSL4 uses the Smart-SSD technology developed by Alibaba Cloud to compress and decompress data at the physical SSD disk level. This can minimize the storage price of data while keeping disk performance consistently high. | 2022-06-21 | |
Cross-region backup | The cross-region backup feature is supported for PolarDB. You can use this feature to back up data from a region to another region for regulation or disaster recovery purposes. You can configure a backup policy to enable the cross-region backup feature. | 2022-06-17 | |
SQL firewall | The SQL firewall feature is supported for PolarDB PolarProxy. This feature can identify SQL statements to be allowed and blocked after you configure blacklist and whitelist rules. | 2022-06-13 |
May 2022
Feature | Description | Release date | References |
IMCI | The IMCI feature is supported. This feature is suitable for online analytical processing (OLAP) scenarios where a large amount of data is processed and complex queries are required. PolarDB for MySQL provides the IMCI feature to enable online transaction processing (OLTP) and OLAP. This integration allows PolarDB for MySQL to function as a one-stop hybrid transaction/analytical processing (HTAP) solution. PolarDB for MySQL allows you to use only one system to meet the requirements of OLTP and OLAP scenarios. | 2022-05-27 |
April 2022
Feature | Description | Release date | References |
Different specifications for primary node and read-only nodes | The primary node and read-only nodes can be separately upgraded or downgraded for a PolarDB cluster. This means that you can select different specifications for the primary node and read-only nodes. | 2022-04-22 | |
Failover with hot standby | The failover with hot standby feature is supported. You can enable hot standby for the read-only nodes in your cluster to improve failover speed and prevent service interruptions. | 2022-04-13 |
March 2022
Feature | Description | Release date | References |
Automatic scaling of local resources | Automatic scaling of local resources is supported for PolarDB for MySQL Cluster Edition clusters. You can configure automatic scaling policies for local resources in the DAS console. When the average CPU utilization of a PolarDB cluster within an observation window reaches the specified threshold, the number of CPU cores of the cluster is automatically increased to the specified value. | 2022-03-23 | |
PolarProxy specification upgrade | The following PolarProxy specification upgrade solutions are provided:
| 2022-03-10 | |
Custom parameters of cluster nodes | Custom parameters can be configured for PolarDB cluster nodes. You can configure the parameters of each cluster node based on your business requirements. | 2022-03-03 |
February 2022
Feature | Description | Release date | References |
New specification for general-purpose clusters of Cluster Edition: 32 cores and 128 GB memory | The following specification is provided for general-purpose clusters of Cluster Edition: 32 cores and 128 GB memory. | 2022-02-18 | Compute node specifications of PolarDB for MySQL Enterprise Edition |
New edition: Multi-master Cluster (Database/Table) Edition | Multi-master Cluster (Database/Table) Edition clusters are developed based on a multi-master architecture that contains multiple primary nodes and read-only nodes. This architecture is suitable for high-concurrency read and write scenarios such as multitenancy, gaming, and e-commerce. To improve the overall concurrent read and write capabilities of clusters, this architecture supports concurrent data writes to databases from different compute nodes and allows you to dynamically switch the primary nodes of databases within seconds. | 2022-02-11 |
December 2021
Feature | Description | Release date | References |
PolarProxy Enterprise Editions | The following PolarProxy Enterprise Editions are available: Standard Enterprise Edition and Dedicated Enterprise Edition.
Compared with the previous free edition of PolarProxy, PolarProxy Enterprise Editions provide additional advanced features such as the multi-master architecture, compute nodes with elastic scaling within seconds, and proxy throttling protection. Note You can use PolarProxy Enterprise Edition free of charge. | 2021-12-09 | |
New edition: X-Engine | X-Engine is developed based on Archive Database (High Compression Ratio). A cluster of X-Engine Edition consists of one primary node and at least one read-only node based on shared storage. The multi-node architecture of X-Engine inherits the advantages of Archive Database (High Compression Ratio), and ensures the high availability of your cluster. If the primary node in your cluster fails, the cluster can automatically fail over to a read-only node. Then, the read-only node serves as the new primary node. This ensures that the service availability is no less than 99.99%. | 2021-12-01 |
November 2021
Feature | Description | Release date | References |
Automatic upgrade and downgrade of subscription PolarDB clusters | Automatic scale-out and scale-in are supported for PolarDB for MySQL subscription clusters. | 2021-11-05 |
October 2021
Feature | Description | Release date | References |
New parameters for the thread pool feature | Multiple parameters, such as bypass_thread_pool_ips and bypass_thread_pool_check_ignore_proxy, are added for the thread pool feature of PolarDB for MySQL 8.0 clusters whose revision version is 8.0.1.1.9 or later. | 2021-10-25 |
August 2021
Feature | Description | Release date | References |
New parameter for PolarDB: polar_replica_work_on_nonblock_mdl_mode | The polar_replica_work_on_nonblock_mdl_mode parameter is supported for PolarDB. You can set this parameter to ON to prevent long-running transactions on PolarDB read-only nodes from blocking DDL operations performed on the primary node. | 2021-08-26 | Prevent long-running transactions on read-only nodes from blocking DDL operations |
Support for the scheduled event feature | The scheduled event feature is supported. You can be notified by text message, phone call, email, or internal message for scheduled PolarDB O&M events. You can also be notified in the PolarDB console. Scheduled PolarDB O&M events include database software upgrade events and hardware maintenance and upgrade events. You can view the details of each scheduled event. These details include the event type, task ID, cluster name, and switchover time. You can also change the switchover time. | 2021-08-06 |
July 2021
Feature | Description | Release date | References |
Specification change of clusters in a global database network (GDN) | 2-core node specifications are not supported by clusters in a GDN. | 2021-07-02 | Compute node specifications of PolarDB for MySQL Enterprise Edition |
Support for database and table restoration for PolarDB for MySQL 5.7 clusters | Databases and tables can be restored from a backup set or to a previous point in time in PolarDB for MySQL 5.7 clusters whose revision version is 5.7.1.0.8 or later. | 2021-07-02 | Method 1 for database and table restoration: Restore data from a backup set and Method 2 for database and table restoration: Restore data to an earlier point in time |
June 2021
Feature | Description | Release date | References |
Support for automatic encryption of new tables in transparent data encryption (TDE) | Automatic encryption of new tables is supported for PolarDB for MySQL 8.0 clusters whose revision version is 8.0.1.1.15 or later. | 2021-06-15 |
May 2021
Feature | Description | Release date | References |
Support for automatic rotation of SSL certificates in SSL configurations | Secure Sockets Layer (SSL) certificates can be automatically rotated in SSL configurations. After automatic certificate rotation is enabled, PolarDB automatically renews the SSL certificate during the maintenance window of the cluster within 10 days before the expiration date of the certificate. | 2021-05-28 |
March 2021
Feature | Description | Release date | References |
Support for the parameter template feature to manage database clusters in a centralized manner | The parameter template feature is supported. You can configure multiple parameters at a time by using a parameter template and apply the template to a PolarDB cluster. | 2021-03-09 | |
Support for enhanced backup to improve data recovery speed | Data backup is optimized for PolarDB. This allows you to create backups every 2, 3, or 4 hours for the data that is generated over the past 24 hours. | 2021-03-09 | |
General-purpose cluster category available for compute nodes | The General-purpose cluster category is supported for PolarDB for MySQL Cluster Edition. This cluster category ensures that idle compute resources such as CPUs are shared among clusters that run on the same server. Resource sharing allows you to deploy a large number of clusters at low costs. | 2021-03-02 | Compute node specifications of PolarDB for MySQL Enterprise Edition |
February 2021
Feature | Description | Release date | References |
Support for the instant ADD COLUMN and statement queue features in PolarDB for MySQL 5.7 clusters | The instant ADD COLUMN and statement queue features are supported for PolarDB for MySQL 5.7 clusters whose revision version is 5.7.1.0.6 or later. You can use the instant ADD COLUMN feature to quickly add columns to large tables and use the statement queue feature to reduce conflict overheads and improve database performance. | 2021-02-09 | |
Faster data recovery | Data recovery is accelerated by the backup and restoration features. The backup and restoration features of PolarDB clusters use multiple threads and other innovative technologies. This allows you to restore data from a backup set (snapshot) to a new cluster within 10 minutes. | 2021-02-09 |
January 2021
Feature | Description | Release date | References |
Archive Database Edition available for commercial use | PolarDB Archive Database Edition is available for commercial use. This edition uses X-Engine to provide a high data compression ratio and reduce storage costs by up to 70%. PolarDB Archive Database Edition is suitable for services that do not require a large number of computing resources but need to store archived data, such as DingTalk messages. PolarDB Archive Database Edition is highly compatible with MySQL and supports the storage capacity of up to 200 TB. | 2021-01-13 | |
Support for two new features: upgrade configurations and node addition on a scheduled basis | Configurations can be upgraded and nodes can be added. When you upgrade cluster configurations or add nodes, you can create a schedule to perform the operation during off-peak hours within 24 hours. The operation may cause short service interruptions. The two features help you reduce the impact of service interruptions. | 2021-01-12 | |
Support for the upgrade of storage plans to increase storage capacity | Storage plans can be upgraded to increase storage capacity. If your storage plan is about to expire or has insufficient storage capacity, you can renew or upgrade the storage plan. | 2021-01-04 |
December 2020
Feature | Description | Release date | References |
Increase in the maximum storage capacity of the nodes of some specifications | The maximum storage capacity of the nodes of some specifications is increased. In PolarDB for MySQL, the maximum storage capacity of 8-core 32 GB nodes is increased to 20 TB. The maximum storage capacity of 16-core 128 GB, 32-core 256 GB, and 64-core 512 GB nodes is increased to 100 TB. | 2020-12-24 | Compute node specifications of PolarDB for MySQL Enterprise Edition |
Task progress bar available in the PolarDB console | The task progress bar is added in the PolarDB console. In the upper-right corner of the PolarDB console, you can click the icon to view the progress of tasks, such as backup and restoration tasks. | 2020-12-03 | N/A |
Support for the restoration of databases and tables in PolarDB for MySQL 5.6 clusters | Databases and tables can be restored in PolarDB for MySQL 5.6 clusters. | 2020-12-01 | |
Support for TDE in PolarDB for MySQL 5.6 clusters | TDE is supported for PolarDB for MySQL 5.6 clusters. | 2020-12-01 |
November 2020
Feature | Description | Release date | References |
Support for storage plans that can be used to offset level-1 backup storage fees | Storage plans can be used to offset fees for the used storage of PolarDB clusters and the used storage that exceeds the free quota for level-1 backups. | 2020-11-27 | Billing rules for backup storage that exceeds the free quota |
September 2020
Feature | Description | Release date | References |
Support for the configuration of time zones and the case sensitivity of table names during cluster creation | The time zones and the case sensitivity of table names can be configured. When you create a PolarDB for MySQL cluster, you can specify whether the table names are case-sensitive. | 2020-09-21 |
August 2020
Feature | Description | Release date | References |
Release of PolarDB for MySQL in the Australia (Sydney) and China (Qingdao) regions | PolarDB for MySQL is officially available in the Australia (Sydney) and China (Qingdao) regions. | 2020-08-21 | |
PolarDB for MySQL 5.7 available for commercial use | PolarDB for MySQL 5.7 is available for commercial use. Users who use PolarDB for MySQL 5.7 during public preview can purchase PolarDB for MySQL 5.7 clusters for their production environments. | 2020-08-21 | |
Release of PolarDB for MySQL in the UK (London) region | PolarDB for MySQL is officially available in the UK (London) region. | 2020-08-15 |
July 2020
Feature | Description | Release date | References |
Support for concurrent addition of multiple read-only nodes on the configuration change page | Multiple read-only nodes can be concurrently added to a PolarDB for MySQL cluster when you change cluster configurations. Approximately 5 minutes is required to concurrently add multiple read-only nodes. | 2020-07-28 | |
PolarDB for MySQL 5.7 available in public preview | PolarDB for MySQL 5.7 is available in public preview. | 2020-07-28 | |
Global read/write splitting available for GDNs | The read/write mode can be set to Read and Write (Automatic Read-write Splitting) for all cluster endpoints in the GDNs of PolarDB for MySQL. Read requests are sent to the on-premises secondary cluster, and write requests are automatically forwarded to the primary cluster in the central region. | 2020-07-01 |
June 2020
Feature | Description | Release date | References |
Switchover with endpoints (connection changes not required) | The Switch with Endpoints (Connection Changes not Required) option can be used to upgrade an existing ApsaraDB RDS for MySQL instance to a PolarDB for MySQL cluster. The original endpoint of the ApsaraDB RDS for MySQL instance can be retained. You do not need to modify the configurations or the code of your applications. | 2020-06-10 |
May 2020
Feature | Description | Release date | References |
Upgrade of the backup feature | The backup feature provided by PolarDB is optimized to deliver more advanced configurations and capabilities to meet enterprise-level data backup requirements. This ensures data security. | 2020-05-12 | |
Backup feature available for commercial use | The backup feature is available for commercial use. You are charged for the storage space occupied by backup files and log files. PolarDB provides a limited quota of free storage space. | 2020-05-12 |
April 2020
Feature | Description | Release date | References |
Release of database services in the Japan (Tokyo) region | PolarDB for MySQL are officially available in the Japan (Tokyo) region. | 2020-04-30 | |
Release of PolarDB for MySQL in the China (Chengdu) region | PolarDB for MySQL is officially available in the China (Chengdu) region. | 2020-04-13 |
March 2020
Feature | Description | Release date | References |
Release of PolarDB for MySQL in the US (Virginia) region | PolarDB for MySQL 5.6 and 8.0 are officially available in the US (Virginia) region. | 2020-03-09 | |
Global consistency | Global consistency is supported by PolarDB for MySQL cluster endpoints. This ensures that the latest data can be retrieved if a replication delay occurs when data is replicated from a primary node to read-only nodes. | 2020-03-03 |
February 2020
Feature | Description | Release date | References |
SSL for encrypted transmission | SSL is supported by the primary endpoints of PolarDB for MySQL clusters. SSL encrypts network connections at the transport layer. This improves data security and integrity but increases network response time. You can enable SSL encryption based on your business requirements. | 2020-02-11 | |
Read requests offloaded from the primary node | Read requests can be offloaded from the primary node in a PolarDB for MySQL cluster. SQL query requests are sent to read-only nodes while data consistency is ensured. This reduces the workloads of the primary node and ensures the stable performance of the primary node. | 2020-02-07 |
January 2020
Feature | Description | Release date | References |
New alert rules | The new alert rule feature (PolarDB for MySQL cluster) is available in CloudMonitor. This feature supports more performance metrics and helps improve user experience in notifications. To obtain better user experience in notifications, we recommend that you use the new alert rules. | 2020-01-09 |
November 2019
Feature | Description | Release date | References |
Support for the diagnostics and optimization features in more regions | The diagnostics and optimization features of PolarDB for MySQL are available in the US (Silicon Valley) and Germany (Frankfurt) regions. The diagnostics and optimization features include the following items:
| 2019-11-19 | |
Release of PolarDB for MySQL in the Malaysia (Kuala Lumpur) region | PolarDB for MySQL 5.6 and 8.0 are officially available in the Malaysia (Kuala Lumpur) region. | 2019-11-14 | |
Support for data migration across zones | Data in PolarDB for MySQL can be migrated across zones. You can use this feature to migrate the compute nodes of a cluster to another zone. This feature is suitable for diverse scenarios. For example, you can use this feature when you perform disaster recovery or enable nearby access for ECS instances. | 2019-11-13 |
October 2019
Feature | Description | Release date | References |
API operations for performance monitoring |
| 2019-10-21 | |
Support for the configuration of node failover priorities | Node failover priorities can be configured in PolarDB. By default, the priority of each node is 1. You can specify an integer from 1 to 15 as the priority. The configuration change takes effect in real time and does not affect the running of database services. | 2019-10-14 | N/A |
Failover | The scheduled failover feature is supported for PolarDB. You can switch the workloads of the primary node to a specified read-only node based on your business requirements. | 2019-10-14 |
September 2019
Feature | Description | Release date | References |
PolarDB for MySQL 8.0 available for commercial use | PolarDB for MySQL 8.0 is available for commercial use. PolarDB for MySQL 8.0 supports parallel queries. In specific scenarios, the performance of your cluster improves by 10 times. You can add fields without the need to lock tables. This significantly reduces the negative impact on service stability. PolarDB for MySQL 8.0 optimizes some features of NoSQL databases, provides an easy way to use JSON data, and adds some advanced SQL features, such as window functions. | 2019-09-12 | |
PolarDB for MySQL available for commercial use | PolarDB for MySQL is available for commercial use in the following regions:
| 2019-09-05 |
August 2019
Feature | Description | Release date | References |
Release of PolarDB for MySQL in the Indonesia (Jakarta) region | PolarDB for MySQL is officially available in the Indonesia (Jakarta) region. | 2019-08-20 |