Skip to content

Conversation

@dpetran
Copy link
Contributor

@dpetran dpetran commented Nov 7, 2025

WIP

Refactors the explain api to be compatible with the :analyze option and to account for heuristic-based optimization in addition to statistical reordering of patterns.

It hasn't been a tuple for years, and we are now showing the pattern name to users via
the explain api, so renaming for consistency.
The explain api should be the same as the query api, and we also will need to support
the :analyze option to report actual query statistics.
Removed the index updating for simple peek/pop as well.
@dpetran dpetran force-pushed the feature/explain-analyze branch 2 times, most recently from 5bb7f0a to cefb5cf Compare November 7, 2025 22:53
The old implementation of explain duplicated all the work from optimize. Now that
optimize is plan-driven, explain can be too.
@dpetran dpetran force-pushed the feature/explain-analyze branch from cefb5cf to 4e11163 Compare November 7, 2025 23:01
@dpetran dpetran force-pushed the feature/explain-analyze branch from 830ceec to d678f32 Compare November 7, 2025 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants