All Products
Search

This Product

    ApsaraDB RDS:Minor engine version updates and release notes for DuckDB-based analytical instances

    Document Center

    ApsaraDB RDS:Minor engine version updates and release notes for DuckDB-based analytical instances

    Last Updated:Mar 28, 2026

    Keep your DuckDB-based analytical instance up to date to get new features, performance improvements, and security fixes. You can apply updates automatically or on demand.

    Release notes

    MySQL 8.0

    Minor versionMySQL versionDescriptionVersion expiration date
    202511288.0.36New features
    • InnoDB partitioned table conversion: Converts InnoDB partitioned tables to DuckDB non-partitioned tables.
    • Hex and binary string literals: DuckDB SQL parses strings that start with x or b, such as x'FF' and b'11111111'.
    • Extended decimal precision: Stores decimal fields with precision greater than 38 digits as decimal(38) in DuckDB.
    • Cross-transaction batch commit control: Adds a switch to control whether cross-transaction batch commits are triggered by the reader, rollback, or length.
    • Checkpoint frequency: Configures the duckdb_checkpoint_threshold parameter to control the frequency of DuckDB checkpoints.
    Performance optimizations
    • Improves append efficiency for Decimal fields.
    Bug fixes
    • Fixes an issue where SQL timeouts caused query results to be truncated.
    • Fixes a community bug where UNION ALL execution unexpectedly hangs. See issue#19971.
    • Fixes data duplication in the DuckDB secondary database when data is written in duckdb_data_import_mode.
    		—
    202511048.0.36New features
    • Cross-transaction batching in binary logging mode: Enables cross-transaction batching when binary logging is active.
    • Regular expression functions: Adds support for REGEXP, REGEXP_INSTR, REGEXP_LIKE, REGEXP_REPLACE, REGEXP_SUBSTR, and RLIKE.
    Performance optimizations
    • Improves replication performance when writing data from Data Transmission Service (DTS) to a DuckDB-based analytical primary instance.
    Bug fixes
    • Fixes a replication interruption caused by DDL statements that specify an algorithm.
    • Supports converting BLOBs to the character type using CAST(blob as CHAR).
    • Fixes an SQL error after a UNION operation on fields with non-binary collation.
    • Fixes an instance crash caused by an append operation.
    • Fixes an issue where temporary tables remain after an engine conversion during the startup phase.
    		—
    202509228.0.36New features
    • Crash-safe binary logging: The DuckDB engine supports crash-safe binary logging.
    • Disabled statements: REPLACE and CREATE TABLE AS SELECT are disabled in the DuckDB engine.
    • JSON functions: The DuckDB engine supports json_unquote, json_contains, and json_contains_path.
    • DuckDB upgrade: Upgraded DuckDB to version 1.3.2.
    Performance optimizationsBug fixes
    • Fixes an issue where the table type was incorrectly identified in recursive Common Table Expressions (CTEs).
    • Fixes an issue where duckdb_maximum_threads did not take effect at startup.
    • Fixes an issue where the DuckDB engine did not respond to a kill command during SQL execution.
    		—

    How updates work

    DuckDB-based analytical instances support two update modes, configurable from the Basic InformationFor more information, see Terms of Service. page.

    Automatic update (default)

    By default, instances are configured to automatically update the minor engine version. When the current version is older than the latest, the system periodically creates an O&M task and runs the update within your configured maintenance window.

    Update notifications are sent through channels such as text messages and emails. To receive them, subscribe to ApsaraDB Fault or O&M Notification in the Message Center and set your contact information. You can cancel the O&M task at any time before it starts — see Scheduled events.

    Manual update

    Switch to Manual Update on the Basic Information page to control when updates are applied. Instances in manual update mode still receive an O&M task if the current version has critical bugs, is expired, or is unpublished.

    Warning

    Automatic updates do not guarantee that all instances are immediately updated to the latest version. Check the engine version status on the Basic Information page and update promptly to avoid risks from outdated versions. If you cancel a system-initiated update task or fail to update to the latest stable version after receiving an update notification in the console, you are responsible for any resulting business interruptions, data loss, or other consequences. For more information, see Terms of Service.

    Usage notes

    • Instance switchover: A minor engine version update may cause an instance switchover. Perform updates during off-peak hours or make sure your application has an automatic reconnection mechanism. See Effects of an instance switchover.

    • No downgrade: You cannot downgrade the minor engine version after an update.

    • Maintenance window: Automatic updates are performed within the maintenance window that you set. You can change the maintenance window on the Basic Information page of the instance.

    • Outdated version risks: Outdated engine versions may cause service interruptions and data loss. Update the minor engine version regularly or after receiving an O&M notification.

    • Newly purchased instances: Update tasks are not pushed to newly purchased instances. To get the latest version, manually update the minor engine version from the Basic Information page.

    • Rollback on failure: The update process cannot be canceled after it starts. If the update fails, all changes are rolled back and the instance retains its previous engine version and metadata.

    • Unpublished versions: When an engine version meets the criteria for being unpublished, its status is set to offline regardless of whether it is still within its lifecycle. An update is also triggered automatically when you upgrade or change the specifications of the instance, or when Alibaba Cloud upgrades the instance hardware.

    Change automatic update settings

    1. Go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.

    2. In the Configuration Information section, click Settings to the right of Minor Engine Version Auto-update.

    3. Select Automatic Update or Manual Update, then click OK.

    Manually update the minor engine version

    1. Go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.

    2. In the Configuration Information section, click Update Minor Engine Version.

      If this button is not displayed, the instance is already on the latest minor engine version.

    3. In the dialog box, select a target version from the Upgradable To list and specify an Upgrade Time. Click OK.

    View update history

    To check update progress or history, open Task Hub in the RDS console. Task Hub shows the task type, status, progress, start time, and end time for both automatic and manual updates from the last 30 days.

    FAQ

    Why doesn't the version number change after an update when I run `SELECT @@version`?

    The update applies to the Alibaba Cloud minor engine version, not the MySQL engine version. Run show variables like '%rds_release_date%' to check your current minor engine version.

    Can I skip versions when updating?

    Yes. You can upgrade to any supported minor version — not just the next one. The console lists all available options in the Upgradable To dropdown.

    Why does an update cause an instance switchover? Are there other risks?

    To maintain service stability, updates use a standby-first approach: the standby instance is updated first, then your service switches over to it. There are no other critical risks. See Effects of an instance switchover for details.

    I changed my instance specifications and the minor engine version was also updated. Why?

    If the instance's engine version is unpublished or no longer maintained, it is automatically updated to the latest minor engine version when you upgrade or change the specifications of the instance, or when Alibaba Cloud upgrades the instance hardware.

    I enabled automatic updates but my instance hasn't been updated. Why?

    Two common reasons: the proxy minor version is too low and must be updated first, or automatic updates are scheduled O&M tasks and are not triggered immediately after a new version is released.

    What happens if I choose not to update?

    Skipping updates means your instance won't receive new features, security patches for known vulnerabilities, or official performance improvements. Update regularly or promptly after receiving an O&M notification.