basalt-26.3.2-rc-20260914: sql/row: TestNextRowPartialColumnFamily failed

sql/row.TestNextRowPartialColumnFamily [failed](https://mesolite.cluster.engflow.com/invocations/default/36252f8d-8f49-40a2-b8b8-d6dd84ae76b7?testReportRun=1&testReportShard=1&testReportAttempt=1#targets-Ly9wa2cvc3FsL3Jvdzpyb3dfdGVzdA==) on basalt-26.3.2-rc-20260914 @ [d3eb08ebdd1dacc8d3dac0b107a7db5929e09969](https://github.com/cockroachdb/cockroach/commits/d3eb08ebdd1dacc8d3dac0b107a7db5929e09969):

```
=== RUN TestNextRowPartialColumnFamily
test_log_scope.go:172: test logs captured to: outputs.zip/logTestNextRowPartialColumnFamily93207225
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.
test_server_shim.go:639: DRPC is enabled (via testserver factory defaults)
```

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

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

Same failure on other branches

- #175421 basalt-26.3.2-rc-20260913: sql/row: TestNextRowPartialColumnFamily failed [OOM] [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260913]
- #174913 basalt-26.3.2-rc-20260908: sql/row: TestNextRowPartialColumnFamily failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3.2-rc-20260908]
- #174741 release-26.3: sql/row: TestNextRowPartialColumnFamily failed [C-test-failure O-robot T-sql-queries branch-release-26.3]
- #174461 basalt-26.3: sql/row: TestNextRowPartialColumnFamily failed [C-test-failure O-robot T-sql-queries branch-basalt-26.3]

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

Start with sql/row.TestNextRowPartialColumnFamily and reproduce the failure using the linked test report, including the race-enabled parameters. Read the relevant test setup and test_server_shim.go, then inspect the captured logs. Done means identifying and fixing the cause so the test passes reliably on the affected branch.

Written by the indexing model from the issue text.