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

你好,关于安全月报中索引的问题 #57

Open
Ovear opened this issue May 11, 2017 · 1 comment
Open

你好,关于安全月报中索引的问题 #57

Ovear opened this issue May 11, 2017 · 1 comment

Comments

@Ovear
Copy link

Ovear commented May 11, 2017

http:https://mysql.taobao.org/monthly/2015/11/10/

这个patch加入到最新版的AliSQL了吗?
这个问题有向MySQL上游提交么?上游是否进行了合并呢?

谢谢。

@xpchild
Copy link
Contributor

xpchild commented May 12, 2017

这个BUG提交给过官方,也verified,在官方5.7.6版本,已经进行了修复。在AliSQL,我们会按照版本迭代加入进去,请关照后续Release。

xpchild pushed a commit that referenced this issue Jan 23, 2018
…slave apply binlog

  Description
  -----------
  In row binlog format, slave chose index when apply binlog use such order:
  1) primary key
  2) unique key without null columns
  3) normal index or unique key with null columns

  Actually, in situation 3 we should chose index with auto_increment column
  first, after this patch, the new order is
  1) primary key
  2) unique key without null columns
  3) normal index with auto_increment columns
  4) normal index without auto_increment columns or unique key with null columns
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants