innodb_fake_changes causes SELECTs to fail if autocommit enabled
Bug #829732 reported by
Valentine Gostev
This bug report is a duplicate of:
Bug #1382745: CREATE table .. SELECT * from <table> fails if destination table is from other SE that is not aware of fake-changes.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Incomplete
|
Medium
|
Unassigned | ||
5.1 |
Won't Fix
|
Medium
|
Unassigned | ||
5.5 |
Triaged
|
Medium
|
Unassigned | ||
5.6 |
Incomplete
|
Medium
|
Unassigned |
Bug Description
mysql> set autocommit=0;
Query OK, 0 rows affected (0.00 sec)
mysql> set innodb_
Query OK, 0 rows affected (0.00 sec)
mysql> select * from t1;
ERROR 1180 (HY000): Got error 131 during COMMIT
Expected to get a valid query result. Same result for insert and update.
Changed in percona-server: | |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
summary: |
- innodb_fake_changes causes error on commit during select + innodb_fake_changes causes error on commit during dml |
tags: | added: xtradb |
tags: | added: fake-changes |
To post a comment you must log in.
In the linked branch patch was included. innodb_ fake_changes_ select added to patch
Test percona_
CURRENT_TEST: main.percona_ innodb_ fake_changes_ select
mysqltest: At line 13: query 'SELECT * FROM t1' failed: 1180: Got error 131 during COMMIT
The result from queries just before the failure was: fake_changes' ; fake_changes= 1; fake_changes' ;
< snip >
INSERT INTO t1 values (123);
SELECT * FROM t1;
a
123
SHOW VARIABLES LIKE 'innodb_
Variable_name Value
innodb_fake_changes OFF
SET innodb_
SHOW VARIABLES LIKE 'innodb_
Variable_name Value
innodb_fake_changes ON