Bug #48162 Partitions: maxvalue in a list partition

• Submitted: 19 Oct 2009 18:16
• Modified: 21 Dec 2009 9:17
• Reporter: Peter Gulutzan
• Status: Closed
• Category: MySQL Server: Partitions
• Severity: S3 (Non-critical)
• Version: 5.4.3-beta
• OS: Linux (SUSE 11.1 64-bit)
• CPU Architecture: Any

[19 Oct 2009 18:16] Peter Gulutzan

Description:
I'm using mysql-trunk-wl3352.
I create a partitioned table.
I alter it so that there is a partition with (maxvalue,maxvalue).
But maxvalue shouldn't be legal in a list partition.

How to repeat:
drop table if exists t7;
create table t7 (s1 int, s2 int) partition by list column_list(s1,s2) (partition p1 values in (column_list(0,0)));
alter table t7 add partition (partition p2 values in (column_list(maxvalue,maxvalue)));

[19 Oct 2009 19:12] MySQL Verification Team

Thank you for the bug report. Verified as described.

[21 Oct 2009 11:50] Peter Gulutzan

> triage: Hi Peter,
>
> What happens after the Alter?
>  - Is it creating a (harmless) partition
No
>  - is there corruption to existing data?
No
>  - Does it affect insert/update/delete/select operations?
Yes. insert/update/delete/select always fail. For example
"
mysql> select * from t7;
ERROR 1064 (42000): Cannot use MAXVALUE as value in List partitioning near 'MAXVALUE,MAXVALUE)) ENGINE = MyISAM)' at line 3
"

[21 Oct 2009 19:00] Mikael Ronström

Verified that the bug is fixed in the
mysql-trunk-wl3352-values tree

[21 Dec 2009 9:17] Mikael Ronström

Was fixed before pushing WL#3352 to any MySQL tree.