New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include PLAN in mon$statements [CORE2303] #2727
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Commented by: @dyemanov In Firebird 3, there are two kind of reported plans: legacy one and new detailed one. Honestly, I'd hate to have them both available in MON$STATEMENTS. Do you think it could be a problem if only the new plan will be reported? |
Modified by: @dyemanovissuetype: New Feature [ 2 ] => Improvement [ 4 ] |
Commented by: @livius2 Dimitry, |
Commented by: @dyemanov Truncated detailed plans will be fixed (after Beta 2). Not every legacy plan can be specified in the SQL text, so it's pretty much useless for any complex query. So I'm still not sure we need to report legacy plans in MON$STATEMENTS. |
Commented by: @livius2 >>Truncated detailed plans will be fixed (after Beta 2). Thank you :) >>Not every legacy plan can be specified in the SQL text, so it's pretty much useless for any complex query. So I'm still not sure we need to report legacy plans in MON$STATEMENTS. Ok - but you can adapt it and then use it |
Submitted by: Douglas Tosi (douglasht)
Is related to QA639
Votes: 5
Currently, if the user wants to know the plan used for a certain statement, [s]he has to prepare the statement on a different attachment.
Depending on the number of statements, this may be an unacceptable overhead.
Plus, there is a change that some index changed after the original statement. The plan could then be different and the analysis compromised.
Please include the statement's PLAN in the monitoring tables. The most straight forward way I can think of is to include a mon$plan field in mon$statements.
Commits: 2c4b4f6 FirebirdSQL/fbt-repository@ca1cc98
The text was updated successfully, but these errors were encountered: