Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report: TableGC will not drop VIEWs #14018

Closed
shlomi-noach opened this issue Sep 19, 2023 · 0 comments · Fixed by #14020
Closed

Bug Report: TableGC will not drop VIEWs #14018

shlomi-noach opened this issue Sep 19, 2023 · 0 comments · Fixed by #14020
Assignees
Labels

Comments

@shlomi-noach
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant