Issue Details (XML | Word | Printable)

Key: CORE-2303
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Douglas Tosi
Votes: 5
Watchers: 5

If you were logged in you would be able to see more operations.
Firebird Core

Include PLAN in mon$statements

Created: 02/Feb/09 06:55 PM   Updated: 28/Sep/15 01:37 PM
Component/s: Engine
Affects Version/s: 2.1.1
Fix Version/s: 3.0 Beta 1

Environment: Every Firebird Version
Issue Links:

QA Status: Done successfully

 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.