[MDEV-19103] [perf] #57 Preferred to chose index with auto_increment column when slave apply binlog Created: 2019-03-31  Updated: 2019-04-02

Status: Open
Project: MariaDB Server
Component/s: Replication
Fix Version/s: None

Type: Task Priority: Major
Reporter: Anel Husakovic Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: RBR

Issue Links:
Relates
relates to MDEV-18745 DDL Algorithm <> Copy could break row... Confirmed
Epic Link: AliSQL patches

 Description   

  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

https://github.com/alibaba/AliSQL/commit/9d1a800eea8df864ea28f1018d895cfd271a3142


Generated at Thu Feb 08 08:49:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.