[no-release-notes] Release v1.1.0

[coffeegoddd]

Created by the Release workflow to update DoltgreSQL's version

[github-actions]

	Main	PR
Total	42090	42090
Successful	18407	18407
Failures	23683	23683
Partial Successes1	5327	5327

	Main	PR
Successful	43.7325%	43.7325%
Failures	56.2675%	56.2675%

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

[github-actions]

	Main	PR
covering_index_scan_postgres	2177.25/s	2173.50/s	-0.2%
groupby_scan_postgres	137.32/s	141.52/s	+3.0%
index_join_postgres	686.92/s	691.58/s	+0.6%
index_join_scan_postgres	904.07/s	905.03/s	+0.1%
index_scan_postgres	31.94/s	32.96/s	+3.1%
oltp_delete_insert_postgres	819.78/s	860.36/s	+4.9%
oltp_insert	782.20/s	796.99/s	+1.8%
oltp_point_select	3786.98/s	3876.88/s	+2.3%
oltp_read_only	3565.49/s	3627.28/s	+1.7%
oltp_read_write	2476.00/s	2513.35/s	+1.5%
oltp_update_index	790.77/s	819.36/s	+3.6%
oltp_update_non_index	860.02/s	876.22/s	+1.8%
oltp_write_only	1795.44/s	1834.02/s	+2.1%
select_random_points	2141.97/s	2147.22/s	+0.2%
select_random_ranges	1638.10/s	1649.64/s	+0.7%
table_scan_postgres	32.19/s	32.89/s	+2.1%
types_delete_insert_postgres	855.28/s	861.37/s	+0.7%
types_table_scan_postgres	14.00/s	14.27/s	+1.9%

[itoqa]

Commit: 817a4cc: 10 test cases ran, 10 passed ✅.

Summary

Coverage focuses on core startup and connection behavior across fresh, reused, restarted, in-memory, and disk-backed environments. It also checks that release, database, and connection identity information stays consistent and that normal database operations and replication compatibility remain healthy.

Safe to merge — the exercised application behaviors are healthy with no PR-attributable regressions, new failures, or previously flagged failures, so there is no merge blocker identified by this run.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Client	A fresh client connected successfully and saw release 1.1.0. The connection remained usable and the standard PostgreSQL version details were still available.
✅	—	Client	The first client and a second client opened after it was closed both received release 1.1.0 and matching server details. Both connections remained usable.
✅	—	Client	The binary and both SQL connections reported release 1.1.0. The first connection and the reconnect showed the same version, with no older value appearing.
✅	—	Startup	A fresh local server created the default database, accepted a PostgreSQL connection, and returned usable database and version metadata.
✅	—	Startup	Both server startup modes became ready and passed their local Go harness checks without errors.
✅	—	Startup	The local server kept the PostgreSQL connection healthy while five repeated metadata checks returned the same version information, and replication compatibility passed.
✅	—	Version	A fresh local connection succeeded and the built-in version check returned 1.1.0 for the postgres database.
✅	—	Version	The local server kept the configured postgres identity and returned release 1.1.0. The available fixture was not a separately created in-memory controller, but the observed identity and release pair matched the expected result.
✅	—	Version	Two separate local connections reported release 1.1.0 with matching SQL server metadata and identity.
✅	—	Version	The persisted local environment and the running server both reported release 1.1.0 with matching database and client identities. No conflicting older release value was served.

Tip

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