[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	1801.85/s	1756.30/s	-2.6%
groupby_scan_postgres	130.50/s	130.34/s	-0.2%
index_join_postgres	630.59/s	633.66/s	+0.4%
index_join_scan_postgres	774.08/s	768.92/s	-0.7%
index_scan_postgres	23.91/s	23.35/s	-2.4%
oltp_delete_insert_postgres	754.96/s	778.02/s	+3.0%
oltp_insert	615.16/s	627.34/s	+1.9%
oltp_point_select	2771.33/s	2758.07/s	-0.5%
oltp_read_only	2838.49/s	2805.51/s	-1.2%
oltp_read_write	2130.30/s	2213.03/s	+3.8%
oltp_update_index	654.69/s	678.60/s	+3.6%
oltp_update_non_index	673.14/s	694.60/s	+3.1%
oltp_write_only	1571.76/s	1665.44/s	+5.9%
select_random_points	1791.88/s	1780.17/s	-0.7%
select_random_ranges	1051.65/s	1051.33/s	-0.1%
table_scan_postgres	22.51/s	22.34/s	-0.8%
types_delete_insert_postgres	691.14/s	715.72/s	+3.5%
types_table_scan_postgres	7.76/s	7.75/s	-0.2%

[itoqa]

Commit: 7d44703: 5 test cases ran, 0 failed ❌, 5 passed ✅, 0 additional findings ⚠️.

Summary

Coverage spans core database lifecycle and reliability behavior: first-time startup and connectivity, normal client session and query flow, resilience to malformed or oversized client input, and storage correctness across rename errors and restarts. Overall health appears stable, with expected failures handled cleanly and data remaining readable after recovery scenarios.

Safe to merge — this PR showed no regressions across the exercised startup, protocol, error-handling, and restart-readability paths, including adversarial input recovery within an active session. With no failing tests and no signs of stability or data-access breakage, the observed merge risk is low.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Binding	A malformed extended-protocol Bind and a structurally valid 8 MB Bind both returned ErrorResponse followed by ReadyForQuery, and the same connection successfully handled SELECT 1 afterward.
✅	—	Bootstrap	With an empty data directory and DOLTGRES_DB=postgres, the server initialized successfully, created the default postgres database, and accepted client connections.
✅	—	Protocol	Server completed the expected PostgreSQL startup handshake sequence and accepted a subsequent SELECT 1 query from the ReadyForQuery state.
✅	—	Storage	ALTER TABLE on a non-existent source table returns a table-not-found error and does not create the destination table name.
✅	—	Storage	After restarting the bumped build against the existing compat fixture, the server accepted connections and returned the baseline row from compat_items without any feature-version or client-out-of-date errors.

Tip

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

[github-actions]

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

	Main	PR
Successful	43.4094%	43.4070%
Failures	56.5906%	56.5930%

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

random

QUERY:          (SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1)
INTERSECT
(SELECT unique1 AS random
  FROM onek ORDER BY random() LIMIT 1);
RECEIVED ERROR: expected row count 0 but received 1

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