Skip to main content

Release notes for Managed Databases

Last update:

2026

June

  • we launched a new DBMS ClickHouse® currently in beta. To check DBMS availability in regions, see the Managed Databases instructions in the Availability Matrix.

    ClickHouse® is a registered trademark of ClickHouse, Inc. https://clickhouse.com;

  • updated the Network block on the cluster creation page — now, when selecting a network, information about routers connected to existing subnets is displayed.

May
April

  • Managed Databases are now available in the multi-AZ pool ru-6. In this pool, you can create clusters with Multi-AZ node placement — nodes are guaranteed to be distributed across different data centers in different availability zones. For more information, see the cluster fault tolerance instructions for the relevant DBMS in the Managed Databases section;

  • we added the ability to manage the maxmemory parameter in Redis version 8. For more information, see the Redis Eviction Policies instructions;

  • changed the price block when creating and scaling an OpenSearch cluster — now it displays prices for each node group;

  • added the jsonb_plperl extension for PostgreSQL and PostgreSQL TimescaleDB.

    Learn more about extensions in the instructions for PostgreSQL and PostgreSQL TimescaleDB.

March
January

  • updated the interface in the Control Panel on the OpenSearch cluster page:

    • simplified how information is presented in node group cards;
    • improved configuration readability.

2025

December

  • added a new version Kafka 4.1;

  • added a new Mega configuration to the Dedicated line:

    • processor: Intel® Xeon® Gold 6336Y 2.4 GHz / Turbo Boost mode 3.6 GHz, 46 vCPU;
    • memory: 706 GB DDR4 ECC Reg;
    • disks: 27.1 TB SSD NVMe, performance — read 1,500,000 IOPS / write 750,000 IOPS, bandwidth — 7,000 MB/s;

  • added new extensions for PostgreSQL and PostgreSQL TimescaleDB:

    • pg_buffercache;
    • clickhouse_fdw;
    • oracle_fdw.

    Learn more about extensions in the instructions for PostgreSQL and PostgreSQL TimescaleDB;

  • added new settings for PostgreSQL, PostgreSQL for 1C, and PostgreSQL TimescaleDB:

    • log_min_duration_statement;
    • log_lock_waits;
    • log_temp_files;
    • track_io_timing;
    • track_functions;
    • transaction_timeout.

    These parameters allow you to flexibly configure logging and monitoring and more accurately analyze DBMS performance under specific load profiles;

  • updated the Control Panel:

    • accelerated cluster loading by region;
    • updated the DBMS and version selection screen on the cluster creation page;
    • updated the Network block and public access configuration for cluster nodes on the cluster creation page.
November

  • added new extensions for PostgreSQL and PostgreSQL TimescaleDB:

    • pg_trgm;
    • tsm_system_rows;
    • tsm_system_time;
    • tcn;
    • plpgsql.

    Learn more about extensions in the instructions for PostgreSQL and PostgreSQL TimescaleDB;

  • added new configurations to the Dedicated line:

    • Micro

      processor: Intel® Xeon® E-2488 3.2 GHz / Turbo Boost mode 5.6 GHz, 14 vCPU;
      memory: 32 GB DDR5 ECC Reg;
      disks: 0.5 TB SSD NVMe, performance — read 700,000 IOPS / write 180,000 IOPS, bandwidth — 7,000 MB/s;

    • Extra Small

      processor: Intel® Xeon® E-2488 3.2 GHz / Turbo Boost mode 5.6 GHz, 14 vCPU;
      memory: 64 GB DDR5 ECC Reg;
      disks: 1 TB SSD NVMe, performance — read 700,000 IOPS / write 180,000 IOPS, bandwidth — 7,000 MB/s;

  • we improved monitoring charts for clusters, nodes, and databases in the Control Panel. Now you can open charts in full-screen mode, enable or disable metrics, and display data from multiple nodes on a single chart;

  • updated interface elements in the Control Panel: text, icons, and spacing;

  • reworked the configuration selection algorithm when creating and scaling a cluster.