feat binlog apply optimization by shaohk · Pull Request #1378 · github/gh-ost

Skip to content

Navigation Menu

Sign in

Appearance settings

Conversation

@shaohk

Description

  1. Support for ignoring binlog events that exceed chunk boundary values.
    If the value corresponding to the unique key of the binlog exceeds the maximum value of chunk iteration and is less than the maximum boundary value of the copy, it is ignored.

  2. Support for binlog merge processing.
    When the columns of the unique key selected by chunk are int or float, the binlog is processed by map merging, and all delete operations are merged into one delete sql.All insert and update operations are merged into one replace sql. Then execute these sql in db transaction.

In case this PR introduced Go code changes:

  • contributed code is using same conventions as original code
  • script/cibuild returns with no formatting errors, build errors or unit test errors.

shaohoukun added 2 commits

February 5, 2024 18:21
1. Support for ignoring binlog events that exceed chunk boundary values. 2. Support for binlog merge
processing.

@shaohk shaohk changed the title (feat): Feat binlog apply optimization Feat binlog apply optimization

Feb 5, 2024

shaohoukun added 3 commits

February 6, 2024 14:39
When there is only one column in a unique index, merging of DML binlog events is permitted.
…tionRangeMaxValues is nil

Add handling for the case when MigrationIterationRangeMaxValues is nil

@shaohk shaohk changed the title Feat binlog apply optimization feat binlog apply optimization

Mar 20, 2024

Labels

2 participants

@shaohk @timvaillancourt