Overview of the Issue

Given a view named _vt_DROP_94c9af2d56cf11eeac590a43f95f28a3_20090920093324 (2009 indicates the expiry year, which is in the past), we expect the table lifecycle (tablegc) mechanism to drop the view.

However, tablegc uses a DROP TABLE statement, which errors out for views.

As result, artifacts of Online DDL's on views are left uncollected:

mysql> show full tables;
+----------------------------------------------------------+------------+
| Tables_in_testdb                                         | Table_type |
+----------------------------------------------------------+------------+
| _vt_DROP_23af3f9007545b1a8388c3945ff2df5c_20230426064348 | VIEW       |
| _vt_DROP_6651e50781f455de895ee766d89863f9_20230426064348 | VIEW       |
| _vt_DROP_f00454b7b22e5b14b7a3305c03745d63_20230426064348 | VIEW       |

Reproduction Steps

run:

CREATE VIEW _vt_DROP_94c9af2d56cf11eeac590a43f95f28a3_20090920093324 AS SELECT 1;

see that it does not get collected.

Binary Version

current, 17, 16, 15

Operating System and Environment details

-

Log Fragments

No response