Release notes for Managed Databases

Last update: June 09 2026

2026

June

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

May

• updated the list of supported PostgreSQL versions: removed version 13 in managed databases PostgreSQL, PostgreSQL for 1C and PostgreSQL TimescaleDB;
• added support for managed databases in audit logs — dbaas service.

April

• managed databases are now available in a multi-AZ pool ru-6. In this pool, you can create clusters with the Multi-AZ node placement type — nodes are guaranteed to be distributed across different data centers in different availability zones. Read more in the Fault Tolerance of a Cluster for a specific DBMS instructions in the Managed Databases section;

• added the ability to manage the maxmemory parameter in Redis version 8. Read more in the Redis eviction policies instruction;

• changed the pricing 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.

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

March

• updated configuration limits for the Flex line. For example, in PostgreSQL;
• added a new version of Redis 8.

January

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

  • simplified information representation in node group cards;
  • improved configuration readability.

2025

December

• added a new version of Kafka 4.1;

• added a new Mega configuration in 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.

  Read 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 flexible configuration of logging and monitoring, as well as more precise analysis of DBMS performance under specific load profiles;

• updated the Control Panel:

  • accelerated cluster loading across regions;
  • 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.

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

• added new configurations in 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;

• improved cluster, node, and database monitoring charts in the Control panel. Now you can open charts in full screen, toggle metrics on or off, and display data for multiple nodes on a single chart;

• updated interface elements in the Control Panel: texts, icons, and padding;

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