[MDEV-9419] CREATE TABLE succeeds w/ read_only mode enabled. Created: 2016-01-14 Updated: 2022-11-06 Resolved: 2022-11-06 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Temporary |
| Affects Version/s: | 5.5, 10.0, 10.1 |
| Fix Version/s: | 10.1.26, 5.5.57, 10.0.32, 10.2.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Michael Eddy | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream-fixed | ||
| Environment: |
Red Hat Enterprise Linux Server release 6.5 (Santiago) |
||
| Attachments: |
|
| Description |
|
When the server is running in read_only mode, and when connected as a user that does not have the SUPER privilege, it is possible to create a real table if a temporary table with the same name already exists.
As you can see, the real table persists. Incidentally, this happens both when binary logging is enabled and when it is not. |
| Comments |
| Comment by Elena Stepanova [ 2016-01-17 ] |
|
Thanks for the report. Also reproducible on MySQL 5.5 and 5.6, fixed in 5.7, apparently in the scope of Bug #64992 |
| Comment by kurt.ding [ 2022-09-30 ] |
|
I check it in mysql8.0 and mariadb10.11 , and this issue is fixed. |
| Comment by kurt.ding [ 2022-09-30 ] |
|
And I check the git history . Here is bug number, so I make a conclusion that this issue has been fixed already. |
| Comment by kurt.ding [ 2022-09-30 ] |
|
This solution is add check before finding the table name in temp table list |
| Comment by Sergei Golubchik [ 2022-11-06 ] |
|
Thanks! Closed. |