You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. ↩
Overall, the unified run passed all 8 of 8 test cases with no failures, showing healthy PostgreSQL wire-protocol behavior end to end across first-start bootstrap, login/handshake readiness, simple query execution, SCRAM authentication, and COPY FROM STDIN ingestion. Key findings were that empty-data-dir startup correctly created and served the default postgres database, sessions remained usable after a recoverable error, valid SCRAM logins succeeded while failed-login responses for existing vs nonexistent users stayed operationally similar, and COPY flows showed correct commit/rollback semantics (including safe retry after mid-stream failure with no duplicate rows) under a controlled local setup that used temporary auth/role-check bypasses and deterministic test credentials.
✅ Passed (8)
Category
Summary
Screenshot
Copy
Created target table, streamed three rows via COPY FROM STDIN, received COPY 3 completion, and verified three committed rows.
Copy
Injected an invalid COPY chunk that failed, verified zero rows remained after failure, retried valid dataset successfully with COPY 3, and confirmed final row count matched expected unique rows.
Login
Valid SCRAM authentication succeeded for the configured test account and returned the authenticated user.
Login
Failed-login responses for existing vs nonexistent users remained operationally similar, with no clear username-enumeration signal observed.
Query
Simple SELECT 1 AS ok; returned one row with normal completion.
Session
Connected with qa_postgres/qa_password and executed SELECT current_database(); returned postgres, confirming startup/login completed and session accepted queries.
Session
In a single PostgreSQL client session, success→error→success statements executed with expected continuity, demonstrating stable session behavior after recoverable error handling.
Startup
Empty data-dir startup bootstrapped the default postgres database and accepted connections.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
☕ 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]
```