You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
151153: sql: disallow pausable portal for procedure call statement r=ZhouXing19 a=ZhouXing19
Fixes#147568
Statement that is a transaction control statement is no longer allowed with pausable portals. Specifically, the following won't be allowed:
```
CALL
PAUSE JOB
PAUSE SCHEDULE
PAUSE JOBS
PAUSE JOBS
COMMIT PREPARED
DEALLOCATE
DISCARD
EXECUTE
ROLLBACK PREPARED
SET TRANSACTION
UNLISTEN
```
Ideally, we should only disallow the CALL statements for procedures that contains mutations. However, the `CanMutate` is not fully propagated from the function body yet. (Issue #147568) For now, we just disallow any TCL statements with pausable portal.
Release note (sql change): Previously, using pausable portal with procedure call caused panic, depending on the function body. Now statements that are transaction control statement, such as procedure call(e.g. `CALL myfunc()`) are not allowed with pausable portal.
151338: opt: return RelExpr from (*memo).RootExpr r=mgartner a=mgartner
`(*memo).RootExpr` now returns a `RelExpr` instead of an `Expr`, helping
eliminate some type assertions.
Release note: None
151491: colexecerror: further optimize BenchmarkSQLCatchVectorizedRuntimeError r=yuzefovich a=yuzefovich
Rather than creating and closing connections for each test case, we can just reuse the same connections in the benchmark, which speeds it up significantly (from about 4 min to 1 min).
Epic: None
Release note: None
Co-authored-by: ZhouXing19 <[email protected]>
Co-authored-by: Marcus Gartner <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments