I am using pt-archiver 3.0.8 (3.0.8-1.stretch) on Debian 9 “Stretch” with mariaDB (10.1.26-0+deb9u1). When using this command:
I am running in the following issue:
The character set seems the same on source and destination.
dbserver.example.local
select * from information_schema.schemata;
±-------------±-------------------±---------------------------±-----------------------±---------+
| CATALOG_NAME | SCHEMA_NAME | DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME | SQL_PATH |
±-------------±-------------------±---------------------------±-----------------------±---------+
| def | fabitest | latin1 | latin1_swedish_ci | NULL |
| def | information_schema | utf8 | utf8_general_ci | NULL |
| def | mysql | utf8mb4 | utf8mb4_general_ci | NULL |
| def | performance_schema | utf8 | utf8_general_ci | NULL |
±-------------±-------------------±---------------------------±-----------------------±---------+
:
select * from information_schema.schemata;
±-------------±-------------------±---------------------------±-----------------------±---------+
| CATALOG_NAME | SCHEMA_NAME | DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME | SQL_PATH |
±-------------±-------------------±---------------------------±-----------------------±---------+
| def | fabitestarchive | latin1 | latin1_swedish_ci | NULL |
| def | information_schema | utf8 | utf8_general_ci | NULL |
| def | mysql | utf8mb4 | utf8mb4_general_ci | NULL |
| def | performance_schema | utf8 | utf8_general_ci | NULL |
±-------------±-------------------±---------------------------±-----------------------±---------+
Can somebody explain how pt-archiver checks the character set?
I used pt-archiver on Debian 8 but with mysql. After upgrading my script isn’t working anymore.
Thanks