Bug #99074 | Fail to do PITR with alter schema statement | ||
---|---|---|---|
Submitted: | 26 Mar 2020 2:49 | Modified: | 24 May 2020 18:47 |
Reporter: | Cai Minshen | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | OS: | Any | |
Assigned to: | MySQL Verification Team | CPU Architecture: | Any |
[26 Mar 2020 2:49]
Cai Minshen
[24 Apr 2020 18:47]
MySQL Verification Team
Hi Cai, What exact version of MySQL 5.7 you can reproduce this on. I tried 5.7.28 and while the binlog looks similar SET @@session.character_set_client=8,@@session.collation_connection=8,@@session.collation_server=8/*!*/; SET @@session.lc_time_names=0/*!*/; SET @@session.collation_database=DEFAULT/*!*/; CREATE DATABASE test05 /*!*/; # at 490 #200326 20:18:52 server id 100 end_log_pos 555 CRC32 0x1fa353c4 Anonymous_GTID last_committed=2 sequence_number=3rbr_only=no SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/; # at 555 #200326 20:18:52 server id 100 end_log_pos 661 CRC32 0xc3940284 Query thread_id=3 exec_time=0 error_code=0 SET TIMESTAMP=1585250332/*!*/; ALTER SCHEMA DEFAULT COLLATE utf8_bin /*!*/; SET @@SESSION.GTID_NEXT= 'AUTOMATIC' /* added by mysqlbinlog */ /*!*/; DELIMITER ; # End of log file /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/; /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/; [arhimed@localdev master]$ point in time recovery has this database properly with default utf8. If you send me your full config files I can try to find out where is the problem. All best Bogdan
[25 May 2020 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".