This repository was archived by the owner on Jan 7, 2025. It is now read-only.
Merged
Conversation
Signed-off-by: Alex Chi Z <iskyzh@gmail.com>
skyzh
force-pushed
the
skyzh/optimizer-structured-trace
branch
from
e7aab86 to
e05b193
Compare
yliang412
approved these changes
Jan 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(See memo_dump.planner.sql for the example)
Compared with the standard log-based trace, structured trace puts all information related to one group together, therefore helping the developer understand what's going on in the system. The trace is appended during apply_rule and optimize_inputs with a step and a stage number, indicating the order of the operations.