[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
covering_index_scan_postgres	1897.37/s	1941.68/s	+2.3%
groupby_scan_postgres	127.87/s	128.15/s	+0.2%
index_join_postgres	667.52/s	670.15/s	+0.3%
index_join_scan_postgres	858.42/s	837.09/s	-2.5%
index_scan_postgres	24.76/s	24.73/s	-0.2%
oltp_delete_insert_postgres	800.15/s	834.75/s	+4.3%
oltp_insert	702.01/s	719.24/s	+2.4%
oltp_point_select	3012.29/s	3023.76/s	+0.3%
oltp_read_only	2984.73/s	3001.64/s	+0.5%
oltp_read_write	2232.90/s	2284.10/s	+2.2%
oltp_update_index	726.71/s	748.17/s	+2.9%
oltp_update_non_index	770.57/s	784.71/s	+1.8%
oltp_write_only	1712.86/s	1777.39/s	+3.7%
select_random_points	1840.45/s	1862.17/s	+1.1%
select_random_ranges	1077.71/s	1078.88/s	+0.1%
table_scan_postgres	23.82/s	23.52/s	-1.3%
types_delete_insert_postgres	765.39/s	776.40/s	+1.4%
types_table_scan_postgres	8.33/s	8.09/s	-2.9%

[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: c9e8a3c: 5 test cases ran, 0 failed ❌, 5 passed ✅, 0 additional findings ⚠️.

Summary

This run exercised core database behavior across startup and initialization, client login and query readiness, prepared-query execution, and merge outcome handling for both normal and conflict-style data changes. It also covered an error-and-recovery path for invalid default database setup, indicating the system handles both expected flows and startup misconfiguration gracefully.

Safe to merge — the reported results show stable behavior in key user-facing database flows and recovery scenarios, with no application failures surfaced by this PR. The covered areas are foundational and include both happy-path and edge-case handling, so current merge risk appears low.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Protocol	With authentication enabled on localhost:5432, both psql and a Node pg client completed SCRAM login, reached ReadyForQuery, and successfully ran SELECT 1.
✅	—	Query	Prepared-statement Parse/Describe/Bind/Execute completed successfully with explicit parameter OID 23 and returned expected row metadata and data; the runner-level blocked status came from a harness hang after completion rather than an application defect.
✅	—	Startup	On a brand-new data directory, startup created exactly one postgres database subtree and subsequent connections reused it without repeated bootstrap creation.
✅	—	Startup	Setting DOLTGRES_DB to an invalid name causes an explicit startup-time SQL error, the server exits cleanly, and restarting on the same data directory with a valid default DB name recovers by creating postgres without leftover invalid-state residue.
✅	—	Storage	Re-verification evidence for all nine merge scenarios matched expected behavior, and the blocked runner status came from a harness execution hang rather than an application defect in merge classification logic.

Tip

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

[github-actions]

This PR has been superseded by #2879