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

[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
Total	42090	42090
Successful	18407	18406
Failures	23683	23684
Partial Successes1	5327	5327

	Main	PR
Successful	43.7325%	43.7301%
Failures	56.2675%	56.2699%

${\color{red}Regressions (1)}$

subselect

QUERY:          select count(*) from tenk1 t
where (exists(select 1 from tenk1 k where k.unique1 = t.unique2) or ten < 0);
RECEIVED ERROR: timeout during Receive

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. ↩

[github-actions]

	Main	PR
covering_index_scan_postgres	2201.59/s	2231.15/s	+1.3%
groupby_scan_postgres	155.77/s	150.90/s	-3.2%
index_join_postgres	705.89/s	709.43/s	+0.5%
index_join_scan_postgres	924.90/s	924.35/s	-0.1%
index_scan_postgres	33.19/s	32.72/s	-1.5%
oltp_delete_insert_postgres	857.08/s	871.96/s	+1.7%
oltp_insert	769.06/s	798.95/s	+3.8%
oltp_point_select	3798.30/s	3863.44/s	+1.7%
oltp_read_only	3716.80/s	3645.06/s	-2.0%
oltp_read_write	2694.64/s	2645.11/s	-1.9%
oltp_update_index	835.31/s	784.70/s	-6.1%
oltp_update_non_index	919.00/s	909.28/s	-1.1%
oltp_write_only	1930.59/s	1897.81/s	-1.7%
select_random_points	2206.74/s	2208.21/s	0.0%
select_random_ranges	1694.69/s	1676.60/s	-1.1%
table_scan_postgres	33.61/s	32.35/s	-3.8%
types_delete_insert_postgres	904.24/s	904.90/s	0.0%
types_table_scan_postgres	14.80/s	14.25/s	-3.8%

[itoqa]

Commit: 43d481e: 14 test cases ran, 14 passed ✅.

Summary

Coverage spans core build and startup behavior, configuration and connection handling, SQL data changes and typed results, array and calendar edge cases, persistence across sessions and restarts, branch isolation, concurrent writes, and safe recovery from rejected operations. The overall product behavior exercised includes normal flows, boundary conditions, error handling, state isolation, and concurrency, with healthy results throughout.

Safe to merge — the exercised application behaviors show no PR-attributable regressions or new failures, including in persistence, concurrency, startup, query compatibility, and edge-case handling. Unrelated environment or setup observations do not constitute merge blockers.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Build	The repository built the doltgres executable successfully with the upgraded dependencies.
✅	—	Build	The complete Go test suite compiled the repository and finished successfully. All packages with tests passed, and the remaining packages reported no test files.
✅	—	Build	The project resolved its dependencies from an isolated cache, built successfully in clean and cached environments, and the clean server accepted a PostgreSQL connection.
✅	—	Query	The server accepted SQL, created and changed a table, and returned the expected row values and PostgreSQL type names.
✅	—	Query	Array comparisons returned the expected true and unknown results, invalid values showed clear errors, and the session still handled a later valid query.
✅	—	Query	Arrays, composite values, timestamps, JSON data, and NULL fields returned correctly. The reported prepared-query error came from using an SQL statement that this server intentionally does not support, not from the client wire-protocol path this test was meant to check.
✅	—	Query	Month-end, microsecond, daylight-saving, timezone, and date-format checks returned the expected rows and displayed values. The apparent parameter failure came from using an unsupported SQL command instead of the supported client parameter protocol.
✅	—	Startup	The server started with its default settings and accepted a PostgreSQL connection on port 5432. A basic query, version check, database and user check, connection privilege check, and public schema check all returned the expected results.
✅	—	Startup	YAML settings and environment-based credentials work as expected. The generated listener failure came from reusing a custom server user while the client still tried the default postgres user.
✅	—	Startup	Three separate connections returned the same database, user, built-in result, and catalog registration. A setting changed in the second connection stayed isolated and did not affect the other connections.
✅	—	Storage	The database created a table and sequence, generated IDs 100 and 101, and showed the same rows and catalog entry from a second session.
✅	—	Storage	The apparent branch-mixing failure could not be confirmed as a product defect. The target server was unavailable for a clean rerun, and source tests cover keeping branch-only objects out of the main branch.
✅	—	Storage	Two sessions inserted 25 rows each, and all 50 rows received different IDs. The rows and highest ID were still present after the database restarted.
✅	—	Storage	Creating a sequence with an existing name returned a clear error. The original sequence and a new retry sequence both kept working, with clean catalog entries and distinct values.

Tip

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

[github-actions]

This PR has been superseded by #3080