Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Inplace Add index with lock=exclusive doesn't generate MLOG_ADD_INDEX redo

Description

Inplace index build using bulk_btr are not redo logged. So server adds MLOG_ADD_INDEX redo to know such case. It is very important for backup tool to know if any transaction happened without redo logging.

When lock=exclusive and algrotithm=inplace is used. Server is not calling

to write MLOG_ADD_INDEX redo.

whereas it works fine with LOCK=Default.

Environment

None

Smart Checklist

Activity

Show:

Rahul Malik February 17, 2022 at 1:01 PM

Problem
Server is not generating MLOG_ADD_INDEX redo in case of inplace add index
with exclusive lock DDL. MLOG_ADD_INDEX tell if any transaction
happened without redo logging. It is very important for backup tool to know if
any transaction happened without redo logging.

Fix:
Generate MLOG_ADD_INDEX if index was created using btr_blk.

Rahul Malik January 12, 2022 at 8:34 AM

The potential fix could be to call finalize() if we building using btr_bulk and not just based if we are building online or not. 

Done

Details

Assignee

Reporter

Upstream Bug URL

https://bugs.mysql.com/bug.php?id=106163

Time tracking

3d 1h 30m logged

Fix versions

Affects versions

Priority

Smart Checklist

Created January 12, 2022 at 8:33 AM
Updated March 6, 2024 at 10:20 AM
Resolved May 13, 2022 at 7:41 AM