[auto-bump] [no-release-notes] dependency by fulghum

[coffeegoddd]

☕ An Automated Dependency Version Bump PR 👑

Initial Changes

The changes contained in this PR were produced by `go get`ing the dependency.

```bash
go get github.com/dolthub/[dependency]/go@[commit]
```

[github-actions]

	Main	PR
covering_index_scan_postgres	2155.54/s	2130.79/s	-1.2%
groupby_scan_postgres	149.85/s	144.67/s	-3.5%
index_join_postgres	691.49/s	691.94/s	0.0%
index_join_scan_postgres	878.50/s	856.64/s	-2.5%
index_scan_postgres	33.02/s	32.40/s	-1.9%
oltp_delete_insert_postgres	855.15/s	885.45/s	+3.5%
oltp_insert	785.11/s	793.43/s	+1.0%
oltp_point_select	3734.21/s	3682.35/s	-1.4%
oltp_read_only	3563.37/s	3527.23/s	-1.1%
oltp_read_write	2764.17/s	2736.70/s	-1.0%
oltp_update_index	799.63/s	775.97/s	-3.0%
oltp_update_non_index	865.20/s	844.88/s	-2.4%
oltp_write_only	1909.99/s	1941.67/s	+1.6%
select_random_points	2253.18/s	2202.38/s	-2.3%
select_random_ranges	1686.41/s	1629.93/s	-3.4%
table_scan_postgres	32.89/s	32.14/s	-2.3%
types_delete_insert_postgres	834.62/s	860.72/s	+3.1%
types_table_scan_postgres	14.68/s	14.72/s	+0.2%

[itoqa]

Commit: ab93aff: 13 test cases ran, 13 passed ✅.

Summary

Coverage spans clean builds and packaged-server usability, core SQL type handling, recovery after malformed or invalid queries, concurrent sessions, restart behavior, configuration safety, in-memory isolation, and durable storage with schema and history preservation. These are primarily happy-path, edge-case, recovery, persistence, and concurrency checks across the server’s main product behaviors.

Safe to merge — the exercised behaviors are healthy with no PR-attributable regressions, new failures, or previously flagged failures. Any evidence-quality caveats are unrelated to the application behavior and are not merge blockers.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Build	The project resolved all modules from an empty cache, compiled the production server, and produced a working Doltgres binary. The documented build wrapper could not run only because Docker was unavailable in the test container.
✅	—	Build	The repository compiled all production and test packages successfully with Go 1.26.2, so the dependency update did not introduce a compile-time break.
✅	—	Build	A clean build produced a usable packaged server. It started with a new data directory, accepted PostgreSQL connections, and completed a create, insert, and query smoke test.
✅	—	Build	Generated test packages passed, and a later query still returned 42 after an intentional missing-table error.
✅	—	Engine	Mixed-type SQL expressions returned the expected values and result types, including integer identity, bigint and numeric widening, directional CASE resolution, and text fallback.
✅	—	Engine	Catalog function metadata and type conversions returned the expected values before and after a malformed query. The malformed query produced a controlled syntax error, and later catalog queries still worked.
✅	—	Engine	Three valid sessions returned the expected bigint and numeric results at the same time. An invalid lookup failed on its own, and later valid queries still returned the correct values and types.
✅	—	Server	A new data directory became ready only after the default database was available. The server accepted a table change, preserved the row after restart, and released port 5432 after both shutdowns.
✅	—	Server	A malformed configuration stopped the server with a clear parse error before it opened port 5432. After the configuration was repaired, the server accepted a PostgreSQL connection and shut down cleanly.
✅	—	Server	The first in-memory server created and queried a temporary table, then stopped. A second server started immediately with no rows from the old table, answered a normal query, and stopped cleanly.
✅	—	Storage	A fresh local server created the sample tables, kept their relationships and rows, and recorded the changes in Dolt history.
✅	—	Storage	After the isolated startup attempt ended, the server came back normally. The default database and employees table were available, two employee rows remained, and the storage status was clean.
✅	—	Storage	After a restart, the database still had all three tables, both foreign keys, the added department column, the original rows, and both commits.

Tip

Reply with @itoqa to send us feedback on this test run.

[github-actions]

This PR has been superseded by #3043

[github-actions]

	Main	PR
Total	42090	42090
Successful	18918	18918
Failures	23172	23172
Partial Successes1	5325	5325

	Main	PR
Successful	44.9465%	44.9465%
Failures	55.0535%	55.0535%

Footnotes

1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩