Bug #13439 Partitions: crash plus database corruption if LESS THAN non-literal
Submitted: 23 Sep 2005 17:37 Modified: 20 Jan 2006 9:44
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.1.2-alpha-debug OS:Linux (SUSE 9.2)
Assigned to: Mikael Ronström CPU Architecture:Any

[23 Sep 2005 17:37] Peter Gulutzan
If I say "LESS THAN (MAX_VALUE)" or "LESS THAN (x1)"
inside a "(PARTITION ...)" clause, I get a crash.
After that, tables in the database are unreadable.

How to repeat:
mysql> create table t100 (s1 int) partition by range(s1) (partition x1 values less than (max_value));
ERROR 2013 (HY000): Lost connection to MySQL server during query
[27 Sep 2005 14:04] Jon Stephens
Same issue except no table corruption apparent. 5.1.2-a_drop5p4-log on SUSE 9.3 and SuSE 10 RC 1.
[20 Oct 2005 18:28] Mikael Ronström
Missed checking return from fix_fields before checking const_item
[19 Jan 2006 9:04] Mikael Ronström
Patch pushed and will appear in 5.1.6
[20 Jan 2006 9:44] Jon Stephens
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

Additional info:

Documented fix in 5.1.6 changelog. Closed.