Bug #17134 Partitions: uncommitted changes are visible
Submitted: 5 Feb 2006 16:34 Modified: 21 Mar 2006 15:58
Reporter: Peter Gulutzan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.1.7-beta-debug OS:Linux (SUSE 10.0)
Assigned to: Assigned Account CPU Architecture:Any

[5 Feb 2006 16:34] Peter Gulutzan
Description:
I create an InnoDB table with partitions.
I have two connections, both REPEATABLE READ.
On one connection, I start a transaction and update, without committing.
On the other connection, I select and see some of what was updated.

How to repeat:
User #1 says:
mysql> create table txm (s1 int, s2 char(5)) engine=innodb partition by list (s1) (partition p1 values in (1), partition p2 values in (2),partition p3 values in (3));
Query OK, 0 rows affected (0.05 sec)

mysql> insert into txm values (1,'a'),(2,'b');
Query OK, 2 rows affected (0.00 sec)
Records: 2  Duplicates: 0  Warnings: 0

User #2 says:
mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> update txm set s1 = s1 + 1;
Query OK, 2 rows affected (0.01 sec)
Rows matched: 2  Changed: 2  Warnings: 0

User #1 says:
mysql> select * from txm;
+------+------+
| s1   | s2   |
+------+------+
|    1 | a    |
|    2 | b    |
|    2 | a    |
+------+------+
3 rows in set (0.00 sec)
[6 Feb 2006 1:03] MySQL Verification Team
Thank you for the bug report.
[20 Mar 2006 21:07] Heikki Tuuri
This is probably the same bug as:

http://bugs.mysql.com/bug.php?id=17992
[21 Mar 2006 15:58] Heikki Tuuri
This indeed is a duplicate of #17992, and the patch I just submitted to that one fixes also this bug.