Bug #118902 no need to set rec_new_set_instant in row_upd_rec_in_place
Submitted: 27 Aug 14:16 Modified: 28 Aug 2:25
Reporter: alex xing (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S5 (Performance)
Version:8.0.42 OS:Any
Assigned to: CPU Architecture:Any

[27 Aug 14:16] alex xing 
Description:
no need to rec_new_set_instant in row_upd_rec_in_place, if the record is already instant record

How to repeat:
just read the code

Suggested fix:
remove rec_new_set_instant in row_upd_rec_in_place
[27 Aug 14:16] alex xing 
a simple patch to describe the optimization

(*) I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: row_upd_rec_in_place_optimize.patch (application/octet-stream, text), 457 bytes.
[28 Aug 2:25] alex xing 
Please ignore this bug report. I was mistaken — I overlooked rec_set_info_bits_new.
[28 Aug 2:25] alex xing 
Please ignore this bug report. I was mistaken — I overlooked rec_set_info_bits_new.