Written by
Updated at March 31, 2026
Data Transfer release notes
2026
February
New features
-
Significantly improved the speed of PostgreSQL-to-PostgreSQL data transfers.
-
Improved database schema migration for PostgreSQL-to-PostgreSQL transfers. Entities are now migrated sequentially based on dependencies between them.
-
Number of VMs allocated for the copy stage will be limited to 64.
Fixed issues
- Improved transfer stability for Apache Kafka® sources.
- Fixed sending metric to Monitoring from the Oracle source.
- Fixed the issue with PostgreSQL-to-PostgreSQL data transfers, where defining the table list at the transfer level (rather than the endpoint) caused the transfer of the entire schema.
- Fixed an issue where simultaneous updates to endpoint and transfer settings via the API and Terraform triggered multiple transfer restarts.
- Fixed the table vacuuming issue for the Managed Service for YDB target.
- Fixed freezes and duplicate delivery of large data volumes during replications from Managed Service for YDB.
- Fixed an issue where deletions failed to propagate to ClickHouse® if columns contained certain types, e.g., UUID.
January
You can now configure Apache Kafka® connections and Data Streams in the Schema Registry data source settings.