For incremental backups for Azure PostgreSQL

You can protect Azure PostgreSQL sever assets with a protection plan and policy. You can use full and differential incremental schedules.
Always set the wal_level server parameter as logical.
The backup user must be an admin user.
The backup user must have the CREATEROLE and REPLICATION permissions.
To backup tables of other users, the tables must have the primary key.
Intelligent groups are supported.
Replica server databases are not supported for full and incremental backups.
Large object data type is not supported for incremental backups.
Incremental backup with the bytea_output server parameter with an escape value is not supported.
Azure SMI and UMI are not supported for incremental backups.
The last value of the sequence generator may not be consistent after restore of an incremental backup.
To rename a database, do the following:
- Note the name of the replication slot created for the database.
  SELECT slot_name FROM pg_replication_slots WHERE database = <database name that needs to be renamed>
- Drop the replication slot after renaming the database.
  SELECT pg_drop_replication_slot('<replication slot name>')