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
This run exercised core database behavior across replication flow and startup, transaction durability and state convergence, schema-change safety checks, and role-based access control boundaries. Coverage included both expected success paths and defensive denial paths, and overall application behavior remained consistent and healthy.
Safe to merge — the exercised functionality showed expected behavior with no failing results, including critical data consistency and authorization guardrails. The current signal indicates low merge risk and no blocker-level regressions in the covered areas.
Tests run by Ito
Result
Severity
Type
Description
✅
—
Permissions
Granted-role CREATE/SELECT/INSERT operations succeeded, while denied-role CREATE/SELECT/INSERT operations returned permission errors, matching the authorization boundary expected for this workflow.
✅
—
Permissions
Manipulating search_path produced permission errors or table-not-found responses for the denied role, and protected table row count remained unchanged.
✅
—
Replication
A cold-start replication run successfully applied INSERT/UPDATE/DELETE changes after COMMIT, and the WAL checkpoint advanced while replica rows matched primary state.
✅
—
Schema
The ALTER TABLE ADD COLUMN statement was correctly rejected with a dependency error, and follow-up queries confirmed both schema and dependent row data remained unchanged.
✅
—
Startup
With complete postgres_replication configuration, startup launched the replication worker and replayed WAL writes to the replica as expected.
Tip
Reply with @itoqa to send us feedback on this test run.
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. ↩
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]
```