MySQL Forums
Forum List  »  Partitioning

Partitioning InnoDB auto_increment bug
Posted by: Reinis Rozitis
Date: March 23, 2007 11:55AM

Recently testing the new partitioning possibilities I came accros such issue:

I have created a simple table:

CREATE TABLE `content_test` (
`cid` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`uid` int(11) unsigned NOT NULL,
PRIMARY KEY (`cid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

PARTITION BY RANGE (cid) (
PARTITION p0 VALUES LESS THAN (10000),
PARTITION p1 VALUES LESS THAN (20000)

)

One simple query is executed:

INSERT INTO content_test SET uid = 123;


If I launch more than one paralel thread (from aplication) which executes this query majority of them fail with 'Can't write; duplicate key in table 'content_test'.

I came accross Bug #18753 http://bugs.mysql.com/bug.php?id=18753 .

Could that be that a similar bug is introduced in 5.1.16 again?

Options: ReplyQuote


Subject
Views
Written By
Posted
Partitioning InnoDB auto_increment bug
4883
March 23, 2007 11:55AM


Sorry, you can't reply to this topic. It has been closed.

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.