Skip to content
  • Abhishek Ranjan's avatar
    c66a2d04
    Bug#26431355 : ALTER TABLE COMMENT FAILS WITH FAILED · c66a2d04
    Abhishek Ranjan authored
                   TO DROP TABLE SDI AFTER UPGRADE
    
    Problem:
    --------
    After upgrade and restart, ALTERs on tables aren't to update SDI.
    The reason is during upgrade, after adding SDI index, InnoDB tablespace
    flags (fsp_flags) are updated. But the fsp_flags are not updated in
    the dd::Tablespace se_private_data. So after restart, tablespace behave
    as if there is no SDI index.
    
    Fix:
    ----
    Change the handlerton APIs from const to non-const dd::Tablespace objects.
    SE will be able to update se_private_data
    
    InnoDB, after updating fsp_flags to dd::Tablespace::se_private_data,
    server updates the dictionary.
    
    Also removed unnecessary call_suppression from main.dd_upgrade_test and
    main.dd_upgrade_error.
    c66a2d04
    Bug#26431355 : ALTER TABLE COMMENT FAILS WITH FAILED
    Abhishek Ranjan authored
                   TO DROP TABLE SDI AFTER UPGRADE
    
    Problem:
    --------
    After upgrade and restart, ALTERs on tables aren't to update SDI.
    The reason is during upgrade, after adding SDI index, InnoDB tablespace
    flags (fsp_flags) are updated. But the fsp_flags are not updated in
    the dd::Tablespace se_private_data. So after restart, tablespace behave
    as if there is no SDI index.
    
    Fix:
    ----
    Change the handlerton APIs from const to non-const dd::Tablespace objects.
    SE will be able to update se_private_data
    
    InnoDB, after updating fsp_flags to dd::Tablespace::se_private_data,
    server updates the dictionary.
    
    Also removed unnecessary call_suppression from main.dd_upgrade_test and
    main.dd_upgrade_error.
Loading