Skip to content
/ server Public

Conversation

@bsrikanth-mariadb
Copy link
Contributor

When the optimizer_record_context=ON save the following into the trace: -

  1. the records_in_range() call arguments, and its output records count in the method ror_scan_selectivity()
  2. the const table rows from join_read_const() using an INSERT statement

Also, when the optimizer_replay_context is SET, read the stored optimizer context from the trace, and do the following: -

  1. execute the INSERT statements to add rows into the respective tables,
  2. fetch output records count using the arguments to records_in_range() method and use them to instead of actually making a call to records_in_range() call from ror_scan_selectivity().

When the optimizer_record_context=ON save the following into the trace:
-
1. the records_in_range() call arguments, and its output records count in the
   method ror_scan_selectivity()
2. the const table rows from join_read_const() using an INSERT statement

Also, when the optimizer_replay_context is SET, read the stored
optimizer context from the trace, and do the following: -
1. execute the INSERT statements to add rows into the respective tables,
2. fetch output records count using the arguments to records_in_range() method
   and use them to instead of actually making a call to records_in_range() call
   from ror_scan_selectivity().
@bsrikanth-mariadb bsrikanth-mariadb force-pushed the 12.3-MDEV-38701-dev-sprint-work-1 branch from c22bb37 to b6a84d6 Compare February 9, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant