basalt-26.3.2-rc-20260908: sql/tests: TestSplitAtTableBoundary failed [OOM]

sql/tests.TestSplitAtTableBoundary [failed](https://mesolite.cluster.engflow.com/invocations/default/4e6b3e4b-4f3a-4ae0-ac38-acabe7fa7d66?testReportRun=1&testReportShard=16&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Rlc3RzOnRlc3RzX3Rlc3Q=) on basalt-26.3.2-rc-20260908 @ [807558e5e81666af257c811e925e4cae570abc28](https://github.com/cockroachdb/cockroach/commits/807558e5e81666af257c811e925e4cae570abc28):

```
=== RUN TestSplitAtTableBoundary
test_log_scope.go:172: test logs captured to: outputs.zip/logTestSplitAtTableBoundary2541468010
test_log_scope.go:82: use -show-logs to present logs inline
test_server_shim.go:168: automatically injected an external process virtual cluster under test; see comment at top of test_server_shim.go for details.
```

Parameters:
- attempt=1
- race=true
- run=1
- shard=16
Help

See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)

[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSplitAtTableBoundary.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/bazci/githubpost/issues)

Start with sql/tests.TestSplitAtTableBoundary and reproduce the failure using the reported race=true, run=1, and shard=16 parameters. Read the test_server_shim.go context and the linked test report and logs; done means identifying the OOM cause and having the test pass reliably under the reported configuration.

Written by the indexing model from the issue text.