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

[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	1824.25/s	1851.32/s	+1.4%
groupby_scan_postgres	135.04/s	136.59/s	+1.1%
index_join_postgres	644.80/s	651.10/s	+0.9%
index_join_scan_postgres	789.52/s	798.03/s	+1.0%
index_scan_postgres	24.52/s	25.31/s	+3.2%
oltp_delete_insert_postgres	797.22/s	786.26/s	-1.4%
oltp_insert	685.68/s	700.95/s	+2.2%
oltp_point_select	2820.07/s	2922.02/s	+3.6%
oltp_read_only	2881.78/s	2943.50/s	+2.1%
oltp_read_write	2303.29/s	2304.16/s	0.0%
oltp_update_index	719.69/s	725.72/s	+0.8%
oltp_update_non_index	741.89/s	768.56/s	+3.5%
oltp_write_only	1731.21/s	1709.80/s	-1.3%
select_random_points	1823.27/s	1867.59/s	+2.4%
select_random_ranges	1070.18/s	1086.46/s	+1.5%
table_scan_postgres	23.29/s	23.71/s	+1.8%
types_delete_insert_postgres	730.18/s	758.97/s	+3.9%
types_table_scan_postgres	8.08/s	8.28/s	+2.4%

[github-actions]

	Main	PR
Total	42090	42090
Successful	18270	18270
Failures	23820	23820
Partial Successes1	5334	5334

	Main	PR
Successful	43.4070%	43.4070%
Failures	56.5930%	56.5930%

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: 21676e2: 10 test cases ran, 0 failed ❌, 10 passed ✅, 0 additional findings ⚠️.

Summary

Coverage spans core database behaviors from connection startup and authentication through normal and malformed query flows, transaction handling, and persistence across reconnects and concurrent schema changes. It also exercises adversarial auth and unsupported-type inputs to confirm failures are controlled and the service remains stable afterward, indicating healthy behavior across happy-path, edge-case, and abuse scenarios.

Safe to merge — the run shows no regressions in critical connection, query, authorization, storage, or error-handling paths, and behavior remains stable under malformed input and concurrency stress. With no failing tests and no signs of application-level breakage, the current change appears low risk for immediate merge.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Authorization	SCRAM authentication succeeds for qa_admin with valid credentials, post-login queries run successfully, and invalid credentials are rejected with controlled FATAL responses.
✅	—	Authorization	Malformed and reordered SASL exchanges fail safely and deterministically, returning controlled FATAL errors or clean connection closes without panics, while the server remains healthy for subsequent valid logins.
✅	—	Query	Extended protocol Parse/Bind/Execute succeeded with parameter OID 0 and text value '1'; the server inferred the bind type from the analyzed plan and returned the expected employee row without ErrorResponse.
✅	—	Query	Extended-protocol Parse/Bind/Execute for BEGIN and COMMIT completed successfully, transaction status transitioned from T to I as expected, and a follow-up SELECT 1 succeeded with no ErrorResponse.
✅	—	Startup	Startup authentication and immediate query execution succeeded for qa_admin on getting_started; the blocked runner status was caused by harness execution instability after completion rather than an application defect in this flow.
✅	—	Startup	The server correctly stays in wait-for-Sync mode after a malformed extended-protocol Parse, returns ErrorResponse before ReadyForQuery, and successfully executes a valid statement after Sync.
✅	—	Startup	Across SSL and GSS fallback startup-ordering scenarios, AuthenticationOk always arrived before ReadyForQuery and post-auth query execution behaved normally. The runner reported this test as blocked due to harness output/timestamp recording failure rather than an application defect.
✅	—	Storage	Renaming rename_src to rename_dst persisted across a new session, and the original row remained available under the new table name.
✅	—	Storage	Concurrent rename/drop and concurrent dual-rename DDL runs completed with coherent final table-map state and preserved row data, with no ghost tables or corruption observed.
✅	—	Type	Unsupported non-doltgres types returned explicit errors during query, cast, and DDL checks, and the server stayed responsive with no panic evidence.

Tip

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

[github-actions]

This PR has been superseded by #2884