Muokkaa

Jaa

Known issues and limitations for the migration service

  • Artikkeli

APPLIES TO: Azure Database for PostgreSQL - Flexible Server

This article describes the known issues and limitations that are associated with the migration service in Azure Database for PostgreSQL.

Common limitations

The following list describes common limitations that apply to migration scenarios:

  • You can have only one active migration or validation to your flexible server.

  • The migration service supports migration for users and roles only when the source is Azure Database for PostgreSQL - Single Server.

  • The migration service shows the number of tables that are copied from the source to the target. You must manually check the data and PostgreSQL objects on the target server after migration.

  • The migration service migrates only user databases. The service doesn't migrate system databases like template_0 and template_1.

  • The migration service doesn't support moving POSTGIS_TOPOLOGY, POSTGIS_TIGER_GEOCODER, POSTGRES_FDW, and PG_PARTMAN extensions from source to target.

    Note

    The feature to migrate databases that have the TIMESCALEDB extension is in preview. The option is turned off by default. To migrate your time series databases, please open a support ticket.

  • You can't move extensions that aren't supported by Azure Database for PostgreSQL - Flexible Server. Supported extensions are listed in Extensions for Azure Database for PostgreSQL.

  • User-defined collations can't be migrated to Azure Database for PostgreSQL - Flexible Server.

  • You can't migrate to an earlier version. For instance, you can't migrate from Azure Database for PostgreSQL version 15 to Azure Database for PostgreSQL version 14.

  • The migration service works only with an SSLMODE value of preferred or required.

  • The migration service doesn't support superuser permissions and objects.

  • Azure Database for PostgreSQL - Flexible Server doesn't support the creation of custom tablespaces due to restrictions on superuser permissions. During migration, data from custom tablespaces in the source PostgreSQL instance is migrated to the default tablespaces of the target instance of Azure Database for PostgreSQL - Flexible Server.

  • The following PostgreSQL objects can't be migrated to a Flexible Server target:

    • Create casts
    • Creation of full-text search (FTS) parsers and FTS templates
    • Users that have superuser roles
    • Create TYPE

  • The migration service doesn't support migration at the object level. That is, you can't migrate a table or a schema.

    Important

    Though the Burstable SKU is not a limitation, it is recommended to choose a higher SKU for your flexible server to perform faster migrations. Azure Database for PostgreSQL - Flexible Server supports near-zero downtime compute and IOPS scaling, so the SKU can be updated with minimal downtime. You can always change the SKU to match the application needs post-migration.

Limitations in migrating from Azure Database for PostgreSQL - Single Server

  • Microsoft Entra users who are on your source server aren't migrated to the target server. To mitigate this limitation, see Manage Microsoft Entra roles. The solution is to manually create all Microsoft Entra users on your target server before you initiate a migration. If Microsoft Entra users aren't created on the target server, migration fails.
  • If the target flexible server uses the SCRAM-SHA-256 password encryption method, connection to a flexible server by using the users or roles on a single server fails. On a single server, passwords are encrypted by using the MD5 algorithm. To mitigate this limitation, for the password_encryption server parameter on your flexible server, select the option MD5.
  • Online migration uses pgcopydb follow. Some logical decoding restrictions apply.

Related content