Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.6 ps bug1395706 #164

Merged
merged 2 commits into from Sep 14, 2015
Merged

5.6 ps bug1395706 #164

merged 2 commits into from Sep 14, 2015

Conversation

kbauskar
Copy link
Contributor

No description provided.

Krunal Bauskar added 2 commits September 11, 2015 09:12
…c line 276

  In fake-change mode database records are not actually modified but the
  modification is assumed and accordingly the path is selected/forced.

  For workload involving ordering change update will be executed as series
  of delete + insert action. Given that fake-change mode is enabled
  actual delete will never happen but path will be selected assuming that
  it took place. Well this can cause to hit some asserts in the forced
  path as the state is not marked. Relax such asserts if fake-change mode
  is enabled.

  One such path that assumed record is marked as deleted when it is not
  is fixed by this patch.
  (rec-del-mark) -> (fake-change || rec-del-mark)
Conflicts:
	mysql-test/r/percona_innodb_fake_changes.result
	mysql-test/t/percona_innodb_fake_changes.test
	storage/innobase/row/row0ins.c
@kbauskar
Copy link
Contributor Author

@laurynas-biveinis
Copy link
Contributor

LGTM

@laurynas-biveinis laurynas-biveinis self-assigned this Sep 14, 2015
kbauskar added a commit that referenced this pull request Sep 14, 2015
@kbauskar kbauskar merged commit 5e63754 into percona:5.6 Sep 14, 2015
@kbauskar kbauskar deleted the 5.6-ps-bug1395706 branch September 14, 2015 04:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants