MySQL Bugs: #16695: Reading I_S.PARTITIONS with pre-5.1.6 partitioned tables crashes server

Bug #16695	Reading I_S.PARTITIONS with pre-5.1.6 partitioned tables crashes server
Submitted:	21 Jan 2006 6:42	Modified:	14 Feb 2006 10:56
Reporter:	Jon Stephens	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Partitions	Severity:	S2 (Serious)
Version:	5.1.6-20060118-bk	OS:	Linux (SuSE 9.3)
Assigned to:	Sergei Glukhov	CPU Architecture:	Any

Description:
See "How To Repeat".

How to repeat:
1. Create partitioned tables in 5.1.5 server, then upgrade to 5.1.6 that uses new partition file naming scheme; OR import table and partition files that were created using 5.1.5 or earlier release to a 5.1.6 server that uses the new partition file naming scheme.

2. mysql> SELECT * FROM INFORMATION_SCHEMA.PARTITIONS;
ERROR 2006 (HY000): MySQL server has gone away

Suggested fix:
Return an error message such as "Incompatible partitioned tables present on server" rather then crashing.

Note: Stopping the server, deleting the pre-5.1.6 table and partition files, and then restarting the server appears to fix the problem. (Quits crashing and you can read the PARTITIONS table after this.)

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/2184

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/2576

Fixed in 5.1.7

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fix/feature change documented in 5.1.7 changelog and 5.1 Manual Partitioning chapter. Bug closed.