MySQL Bugs: #36249: Timing dependency bug in falcon_bug

Bug #36249	Timing dependency bug in falcon_bug_22183
Submitted:	22 Apr 2008 10:50	Modified:	9 Oct 2008 11:51
Reporter:	Vladislav Vaintroub	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S3 (Non-critical)
Version:	6.0	OS:	Any
Assigned to:	Vladislav Vaintroub	CPU Architecture:	Any

Description:
falcon_bug_22183 tests 2 parallel inserts  in transaction context 
in the first transaction insert is followed by "alter table" that tries to define primary key second time and should fail with "multiple primary key definition"
 
The test however does not take into account that alter table implicitely commits the transaction.

Thus the result of "alter" might also be "table locked", if parallel running transaction manages to do an insert in between commit and alter

How to repeat:
look at the pushbuild results for this test in falcon-team tree. 
On fast  machines "table locked" is returned on ALTER, on slow machines "multiple primary key"

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

ChangeSet@1.2635, 2008-04-22 12:54:14+02:00, vvaintroub@wva. +3 -0
  Bug#36249 : correct timing dependency in test case
  Also, comment out tests that will not be fixed in the long run.

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

ChangeSet@1.2635, 2008-04-22 13:07:35+02:00, vvaintroub@wva. +3 -0
  Bug#36249 : correct timing dependency in test case
  Also, comment out tests that will not be fixed in the long run.

Appears to be test failure only, with no user-facing changes. Closed bug report without taking any further action.