Bug #19392 Rename Database: Crash if case change
Submitted: 27 Apr 2006 1:40 Modified: 13 Jul 2006 3:47
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Locking Severity:S3 (Non-critical)
Version:5.1.10-beta-debug OS:Linux (SUSE 10.0)
Assigned to: Alexander Barkov CPU Architecture:Any

[27 Apr 2006 1:40] Peter Gulutzan 
Description:
I create a database named A.
I rename it to a. Notice that this is the lowercase variant of A.
Crash.

How to repeat:
mysql> create database A;
Query OK, 1 row affected (0.00 sec)

mysql> rename database A to a;
ERROR 2013 (HY000): Lost connection to MySQL server during query
[27 Apr 2006 2:48] MySQL Verification Team 
Thank you for the bug report.

060427 23:48:51 [Note] /home/miguel/dbs/5.1/libexec/mysqld: ready for connections.
Version: '5.1.10-beta-debug'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
[New Thread 1118682032 (LWP 5718)]
mysqld: sql_db.cc:138: void lock_db_delete(const char*, uint): Assertion `opt != __null' failed.

Program received signal SIGABRT, Aborted.
[Switching to Thread 1118682032 (LWP 5718)]
0xffffe410 in __kernel_vsyscall ()
(gdb)
[18 May 2006 7:29] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6552
[18 May 2006 7:35] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/6553
[7 Jun 2006 9:12] Sergei Glukhov 
ok to push
[7 Jul 2006 6:59] Alexander Barkov 
Pushed into 5.1.12.
[13 Jul 2006 3:46] Paul DuBois 
Noted in 5.1.12 changelog.

Renaming a database to itself caused a server crash.