we’re testing migration of postgres running on a VM to azure flexible server using the migration option in the portal. On the validation it fails saying
Error 603401: Collation mismatch. Collation en_GB.UTF8 in database xxxxxx is not present on target server.
Flexible server has collation en_GB.utf8 (lowercase) in pg_collations but not en_GB.UTF8 (uppercase). However, I can create a database with en_GB.UTF8.
Is UTF8 the same as utf8? Should we abandon the migration option and just do a dump/restore into a database created with UTF8?
New contributor
DNA is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.