Bug #35788 | A few tests fail due to concurrent inserts | ||
---|---|---|---|
Submitted: | 3 Apr 2008 8:33 | Modified: | 6 May 2008 18:32 |
Reporter: | Alexander Nozdrin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tests: Server | Severity: | S7 (Test Cases) |
Version: | 5.1-bk | OS: | Any |
Assigned to: | Davi Arnaut | CPU Architecture: | Any |
[3 Apr 2008 8:33]
Alexander Nozdrin
[3 Apr 2008 8:35]
Alexander Nozdrin
Grr... Suggested fix is obviously: SET CONCURRENT_INSERT = 0; Sorry for the mess.
[7 Apr 2008 14:24]
Susanne Ebrecht
Verified as described.
[30 Apr 2008 13:28]
Bugs System
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/46225 ChangeSet@1.2573, 2008-04-30 10:28:19-03:00, davi@mysql.com +6 -0 Bug#35788 A few tests fail due to concurrent inserts The problem is that since MyISAM's concurrent_insert is on by default some concurrent SELECT statements might not see changes made by INSERT statements in other connections, even if the INSERT statement has returned. The solution is to disable concurrent_insert so that INSERT statements returns after the data is actually visible to other statements.
[30 Apr 2008 16:03]
Davi Arnaut
Queued to 5.1-bugteam
[6 May 2008 0:29]
Bugs System
Pushed into 5.1.25-rc
[6 May 2008 0:33]
Bugs System
Pushed into 6.0.6-alpha
[6 May 2008 18:32]
Paul DuBois
Test suite changes. No changelog entry needed.