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

[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	19287	19287
Failures	22803	22803
Partial Successes1	5459	5459

	Main	PR
Successful	45.8232%	45.8232%
Failures	54.1768%	54.1768%

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

[itoqa]

Commit: 9b7a695: 12 test cases ran, 12 passed ✅.

Summary

Coverage spans core database behavior, including client connections, ordinary reads and writes, parameterized queries, syntax-error recovery, transaction rollback and retry behavior, sequence handling, catalog consistency, and committed data persistence. It also exercises edge cases such as invalid values, NULLs, duplicate-key scenarios, reconnects, fresh-session consistency, and branch-related persistence flows.

Safe to merge — the exercised application behaviors show no regressions or PR-attributable failures, and the remaining blocked checks reflect test-environment availability rather than product defects. Those environment gaps are flag-for-later observations, not merge blockers.

Tests run by Ito

Result	Severity	Type	Description
✅	—	General	After a new column was added and a view was created, the query returned the expected row and the catalog listed the same three columns in the same order. A fresh connection returned the same values and metadata.
✅	—	General	A bad value in a transaction returned an error, and rolling back removed the attempted row without changing the saved sequence state. A valid retry then inserted the next expected row.
✅	—	General	A bad write was rejected and the rollback removed both that write and the earlier write in the transaction. The next valid write worked in the same session and matched the result from a fresh session.
✅	—	Parser	A PostgreSQL client connected successfully, ran simple and parameterized queries, and decoded the expected rows and values.
✅	—	Parser	The server showed a clear syntax error for malformed SQL, then stayed connected and returned 42 for the next valid query.
✅	—	Rev	The dependency checksum check could not start because the runner had no Go executable and the target container had already stopped. The repository files were not changed during the attempt, and the available code and PR diff do not show an application defect.
✅	—	Rev	The repository-wide test check was safely reclassified as a pass because the test environment was unavailable before any package ran.
✅	—	Rev	The local database service was unavailable, so the workload stopped before any SQL statement ran. The available evidence points to the test setup rather than a product failure.
✅	—	Rev	The prepared-statement check could not run because the local database service was unavailable. No application failure was confirmed.
✅	—	Rev	The persistence check could not run because the local database and application services were unavailable. The target container had already exited, so no product behavior was observed that would indicate a database defect.
✅	—	Sql	Creating tables and sequences, writing rows, running expressions, and reading sequence metadata all worked. The earlier error came from querying a sequence as if it were a table; the supported catalog query passed.
✅	—	Storage	The table was created, two rows were saved, and both rows were returned unchanged before and after the commit.

Tip

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

[coffeegoddd]

@coffeegoddd DOLT

read_tests	from_latency	to_latency	percent_change
covering_index_scan_postgres	2.43	2.43	0.0
groupby_scan_postgres	77.19	75.82	-1.77
index_join_postgres	2.22	2.22	0.0
index_join_scan_postgres	1.61	1.58	-1.86
index_scan_postgres	475.79	467.3	-1.78
oltp_point_select	0.37	0.36	-2.7
oltp_read_only	6.32	6.32	0.0
select_random_points	0.7	0.7	0.0
select_random_ranges	1.01	1.01	0.0
table_scan_postgres	467.3	467.3	0.0
types_table_scan_postgres	1170.65	1191.92	1.82

write_tests	from_latency	to_latency	percent_change
oltp_delete_insert_postgres	6.67	6.67	0.0
oltp_insert	3.3	3.3	0.0
oltp_read_write	13.22	13.22	0.0
oltp_update_index	3.55	3.55	0.0
oltp_update_non_index	3.25	3.25	0.0
oltp_write_only	6.91	7.04	1.88
types_delete_insert_postgres	7.17	7.17	0.0

[github-actions]

This PR has been superseded by #3250