Bug #13441 Partitions: failure with analyze statement
Submitted: 23 Sep 2005 17:40 Modified: 20 Jan 2006 9:54
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:40] Peter Gulutzan
With InnoDB, "ANALYZE non_partitioned_table" results in
"Table is already up to date" but "ANALYZE partitioned_table"
results in "The storage engine for the table doesn't support
analyze". My only complaint is that the message is false.

How to repeat:
mysql> create table tpay (s1 int, unique (s1)) engine=innodb partition by list (s1) (partition x1 VALUES in (10), partitionx2 values in (20));
Query OK, 0 rows affected (0.01 sec)

mysql> analyze table tpay;
| Table    | Op      | Msg_type | Msg_text                                                 |
| db3.tpay | analyze | note     | The storage engine for the table doesn't support analyze |
1 row in set (0.00 sec)
[2 Nov 2005 18:10] Mikael Ronström
Analyze error message was correct in 5.1.2
In partition management clone in review, analyze table is supported for
partitioned tables
[19 Jan 2006 9:03] Mikael Ronström
Patch pushed and will appear in 5.1.6
[20 Jan 2006 9:54] 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 feature change in 5.1.6 changelog. Closed.