[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]

This PR has been superseded by #3243

[github-actions]

	Main	PR
Total	42090	42090
Successful	19271	19270
Failures	22819	22820
Partial Successes1	5459	5459

	Main	PR
Successful	45.7852%	45.7828%
Failures	54.2148%	54.2172%

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

copyselect

QUERY:          drop table test3;
RECEIVED ERROR: COPY DATA message received without a COPY FROM STDIN operation in progress

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: c3b0232: 14 test cases ran, 14 passed ✅.

Summary

Coverage spans core database behavior, including creating and reading data, persistence across reconnects and branches, concurrent writes, joins and result shapes, dependency compatibility, and driver integration. It also exercises edge and recovery paths such as malformed or failed statements, rollback, merge conflicts, and session recovery, with healthy results across both normal and adversarial flows.

Safe to merge — the exercised application behaviors are healthy across persistence, transactions, branching, concurrency, compatibility, and error recovery, with no PR-attributable regressions or unresolved failures. Any evidence limitations are not application failures and do not present a merge blocker.

Tests run by Ito

Result	Severity	Type	Description
✅	—	General	A successful insert was visible right away and after opening a fresh connection, so both client views showed the same committed row.
✅	—	General	The invalid second statement rolled back the earlier insert, and the corrected retry committed exactly one intended row.
✅	—	General	After a merge failed, reopening the database kept the conflict details and every branch row. Choosing the local version cleared the conflict and created the intended final commit.
✅	—	Dolt	A table was created, filled with two rows, and committed. A fresh connection returned the same columns, values, and commit message.
✅	—	Dolt	The merge reported the expected conflict, kept the nonconflicting rows from both branches, and preserved accurate conflict details. The earlier autocommit attempt rolled back safely without leaving an unresolved durable merge.
✅	—	Rev	The upgraded dependencies resolve to the versions declared by the change, and their checksums verify successfully.
✅	—	Rev	An invalid statement returned the expected error, rollback completed, and a later parameterized insert on the same connection succeeded. The final query returned exactly row 42.
✅	—	Rev	Committed data stayed on the correct branch. The main branch kept its original row, while the second branch kept both rows after switching away and back.
✅	—	Rev	Two separate connections inserted different rows and committed successfully. A third connection found all four rows, with each primary-key value present exactly once.
✅	—	Rev	A query joined two source rows with generated values and returned the expected names, types, and values. An empty generated result returned no rows while keeping its declared columns.
✅	—	Sql	The database created a table, inserted and returned rows, evaluated expressions, rolled back a transaction, ran a function, and returned the expected error for invalid SQL.
✅	—	Sql	The engine compatibility suite completed successfully and reported a passing package result.
✅	—	Sql	The Go SQL driver built successfully and completed its integration suite against the local Doltgres server. Queries, writes, transactions, and error handling worked as expected.
✅	—	Sql	A malformed query showed a syntax error, but the same session stayed usable. The follow-up query and insert returned the expected rows, with no extra data left behind.

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.52	2.43	-3.57
groupby_scan_postgres	77.19	75.82	-1.77
index_join_postgres	2.26	2.22	-1.77
index_join_scan_postgres	1.58	1.61	1.9
index_scan_postgres	475.79	475.79	0.0
oltp_point_select	0.36	0.36	0.0
oltp_read_only	6.43	6.32	-1.71
select_random_points	0.7	0.72	2.86
select_random_ranges	1.01	1.03	1.98
table_scan_postgres	467.3	475.79	1.82
types_table_scan_postgres	1191.92	1191.92	0.0

write_tests	from_latency	to_latency	percent_change
oltp_delete_insert_postgres	6.67	6.67	0.0
oltp_insert	3.36	3.36	0.0
oltp_read_write	13.46	13.46	0.0
oltp_update_index	3.62	3.62	0.0
oltp_update_non_index	3.25	3.25	0.0
oltp_write_only	7.04	7.04	0.0
types_delete_insert_postgres	7.17	7.17	0.0