. . . . . . . . 299 Percona FOSS Talks 2021 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 FOSDEM 2021 . . . . . . . . . . . . . . . . . . . . 6. At this time we point out that 20200911234156 is actually a readable timestamp, and stands for 2021-02-11 23:41:56. That timestamp can tell us when the table was last renamed. Vitess can then run an 17 Feb 2021 13:09:54 GMT Content -Type: text/html; charset=utf-8 Starting MySQL for tablet zone1 -0000000101... Starting vttablet for zone1 -0000000101... HTTP/1.1 200 OK Date: Wed, 17 Feb 2021 13:10:03

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Perconalive 2021 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 13 Percona FOSS Talks 2021 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 FOSDEM 2021 . . . . . . . . . . . . . . . . . . . . 6. At this time we point out that 20200911234156 is actually a readable timestamp, and stands for 2021-02-11 23:41:56. That timestamp can tell us when the table was last renamed. Vitess can then run an

. . . . . . . . 277 Percona FOSS Talks 2021 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 FOSDEM 2021 . . . . . . . . . . . . . . . . . . . . 6. At this time we point out that 20200911234156 is actually a readable timestamp, and stands for 2021-02-11 23:41:56. That timestamp can tell us when the table was last renamed. Vitess can then run an 17 Feb 2021 13:09:54 GMT Content -Type: text/html; charset=utf-8 Starting MySQL for tablet zone1 -0000000101... Starting vttablet for zone1 -0000000101... HTTP/1.1 200 OK Date: Wed, 17 Feb 2021 13:10:03

6. At this time we point out that 20200911234156 is actually a readable timestamp, and stands for 2021-02-11 23:41:56. That timestamp can tell us when the table was last renamed. Vitess can then run an supports Percona Server for MySQL versions 5.6 to 8.0. With MySQL 5.6 reaching end of life in February 2021, it is recommended to deploy MySQL 5.7 and later. MariaDB versions 10.0 to 10.3 Vitess supports names. Examples: • The table _vt_HOLD_6ace8bcef73211ea87e9f875a4d24e90_20210915120000 is held until 2021-09-15 12:00:00. The data remains intact. • The table _vt_PURGE_6ace8bcef73211ea87e9f875a4d24e90_20210915123000

supports Percona Server for MySQL versions 5.6 to 8.0. With MySQL 5.6 reaching end of life in February 2021, it is recommended to deploy MySQL 5.7 and later. MariaDB versions 10.0 to 10.3 Vitess supports

supports Percona Server for MySQL versions 5.6 to 8.0. With MySQL 5.6 reaching end of life in February 2021, it is recommended to deploy MySQL 5.7 and later. MariaDB versions 10.0 to 10.3 Vitess supports

supports Percona Server for MySQL versions 5.6 to 8.0. With MySQL 5.6 reaching end of life in February 2021, it is recommended to deploy MySQL 5.7 and later. MariaDB versions 10.0 to 10.3 Vitess supports