[MDEV-20642] Orphan procedure remains in mysql.proc after dropping database Created: 2019-09-21 Updated: 2019-09-21 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Procedure, Server |
| Affects Version/s: | 5.5, 10.1, 10.2, 10.3, 10.4 |
| Fix Version/s: | 10.4 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Oleksandr Byelkin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | upstream | ||
| Description |
|
The test below runs DROP DATABASE and kills the connection which runs it. Then it runs DROP DATABASE again, to ensure it is really dropped if it hadn't been yet. However, a procedure which was previously created within the dropped database survives and stays in mysql.proc. The test is non-deterministic, run with --repeat=N. It currently fails for me every time, but it can vary on different machines and builds.
Reproducible on all of MariaDB and at least on MySQL 5.7 (8.0 doesn't seem to have mysql.proc). |