-
Notifications
You must be signed in to change notification settings - Fork 479
DOC-15477: Product Change- PR #156905 - sql: Record statement stats for statements executed in UDFs / SPs #21621
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
base: main
Are you sure you want to change the base?
Conversation
… statistics section. In routine-limitations.md, added limitation for statement diagnostics. In statements-views.md, added callout that statements include those executed in UDF/SPs. In transaction-diagnostics.md, added callout about limitation for statement diagnostics.
Files changed:
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
|
@kyle-a-wong , please review and let me know what is the issue number for the limitation. thanks! |
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| {{site.data.alerts.callout_info}} | ||
| Transaction diagnostics cannot be collected for statements executed within [user-defined functions]({% link {{ page.version.version }}/user-defined-functions.md %}) or [stored procedures]({% link {{ page.version.version }}/stored-procedures.md %}). Transaction diagnostics continue to work only for top-level statement executions. | ||
| {{site.data.alerts.end}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better phrased as something like: "Transaction diagnostics will not contain a statement diagnostic bundle for statements executed in udfs / sps, but will contain a bundle for the top level udf / sp invocation (or call)"
| These statements will also appear in the [**Transaction details**]({% link {{ page.version.version }}/ui-transactions-page.md %}#transaction-details-page) in the **Statement Fingerprints** table when the stored procedure is invoked as part of a transaction. | ||
|
|
||
| {{site.data.alerts.callout_info}} | ||
| Statement diagnostics cannot be collected for statements executed within stored procedures. Statement diagnostics continue to work only for top-level statement executions. For details, see [Known limitations](#known-limitations). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure where exactly it should live in this document, but I want to note that statement diagnostics can be requested for the top level UDF / SP statement, and the trace will contain spans for each statement executed. There is just no way (currently) to get specific to have statements executed in the UDF / SP to fulfill an open statement diagnostics request.
| These statements will also appear in the [**Transaction details**]({% link {{ page.version.version }}/ui-transactions-page.md %}#transaction-details-page) in the **Statement Fingerprints** table when the UDF is invoked as part of a transaction. | ||
|
|
||
| {{site.data.alerts.callout_info}} | ||
| Statement diagnostics cannot be collected for statements executed within UDFs. Statement diagnostics continue to work only for top-level statement executions. For details, see [Known limitations](#known-limitations). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here as i mentioned in the stored procedure doc
Fixes DOC-15477
Rendered preview