use original se_private_data during DDSE change early steps

[luqun]

Summary:

INNODB hit crash during DDSE change due to use wrong root page/index_id calculated from DD tables private data.

mysqld`rec_get_offsets
mysqld`btr_estimate_number_of_different_key_vals(index=0x00007fffab987c88)
mysqld`dict_stats_update_transient_for_index
mysqld`dict_stats_update_transient
mysqld`dict_stats_update
mysqld`dict_stats_init
mysqld`ha_innobase::open
mysqld`handler::ha_open
mysqld`open_table_from_share
mysqld`open_table

During DDSE change(such as INNODB to ROCKSDB), it will

1. populate existing DD tables in mysql with INNODB,
2. create these DD tables in with ROCKSDB
3. copy data form INNODB DD tables into ROCKSDB DD tables

Even in step1:

• Before this fix, it will calculate index ids/root pages through handle API and ignore se_private_data stored in dd_properties table. if these index ids/root pages are same, then everything are okay. but if these index ids and root pages has been changed(such as mysql.columns index ids changed from 22,23,24 to 600,601,602), then we use wrong index ids/root pages to read page..

• With this fix, always use se_private_data stored in dd_properties table to populate these DD tables(or didn't call handler API to calculate se_private_data again).

Test Plan:

Reviewers:

Subscribers:

Tasks:

Tags:

[facebook-github-bot]

@luqun has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.