Expand description
SQL statement execution, transaction boundaries, and batch scheduling.
Modules§
- batch
- SQL batch scheduling over live cache, transaction and statement inputs.
- compiled
- Execute compiled statements with planning and statement scopes captured at their point of use.
- context
- Compose native statement execution from its query, schema, routine and session inputs.
- cursor
- Single-query scheduling that seals a bounded result before committing its snapshot.
- notifications
- Admission and execution policy for session-owned SQL notification listeners.
- plan_
executor - Exhaustive physical executor for the unified SQL plan.
- portal
- Session portal declaration and native row-streaming execution.
- prepared
- Prepared registration ordered around retained session registry publication.
- show
SHOW nameandSHOW ALL, asPostgreSQL’sGetPGVariablereports them: one text column named after the parameter’s canonical spelling, or the name, setting and description of every parameter thatSHOW ALLlists.- table_
locks - Ordered explicit table locks, binding rechecks, inheritance and view authorization.
- thread_
context - The thread-local inputs and cancellation of one running statement, which the statement enters where it runs and each thread that runs part of it enters before that work.
- thread_
scope - Restore a thread’s statement temporal input, cancellation and retained regex cache when the work that entered them ends.
- transactions
- Read-only validation, snapshot marking, and statement failure cleanup.
- validation
- Cancellation and SQL validation before any command-specific state is observed.