Bug #44620 Long Key Cache name is not allowed with no warnings

Submitted:	2 May 2009 3:36	Modified:	2 May 2009 13:40
Reporter:	Peter Zaitsev (Basic Quality Contributor)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S3 (Non-critical)
Version:	5.0, 5.1-bzr	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
If you try to create long key cache name it is not created:

How to repeat:
localhost:(none)> set global  aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.key_buffer_size=1000000;
Query OK, 0 rows affected (0.00 sec)

localhost:(none)> select @@aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.key_buffer_size;
+-----------------------------------------------------------------------------+
| @@aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.key_buffer_size |
+-----------------------------------------------------------------------------+
|                                                                           0 |
+-----------------------------------------------------------------------------+

Compare to short name:

localhost:(none)> set global  a.key_buffer_size=1000000;
Query OK, 0 rows affected (0.00 sec)

localhost:(none)> select @@a.key_buffer_size;
+---------------------+
| @@a.key_buffer_size |
+---------------------+
|              999424 |
+---------------------+
1 row in set (0.00 sec)

Suggested fix:
Make name size to match max allowed table size as (or longer) as it is often convenient to name key caches by tables.

Thank you for the bug report. Verified just as described also with recent 5.1 from bzr.

Page generated in 0.049 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.