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 exercises core database metadata behavior end to end, including object lifecycle operations, identity mapping consistency, restart stability, and concurrent session isolation under contention. It also covers boundary handling for maximum-length identifiers, and overall behavior remained stable with clean state management across these functional and edge-case paths.
Safe to merge — this run shows no regressions, no new failures, and no still-failing issues attributable to this PR, while validating both normal flows and higher-risk concurrency and boundary conditions.
Tests run by Ito
Result
Severity
Type
Description
✅
—
Buffer
Schema-scoped create and drop operations for tables, sequences, and functions completed successfully, with stable OID lookups across repeated catalog reads and clean object removal at the end.
✅
—
Buffer
Catalog and lookup paths stayed consistent for all created objects, with 7/7 cross-path OID identity checks returning MATCH and clean teardown after drop.
✅
—
Concurrent
Catalog OIDs for built-in types, namespaces, and relations remained identical across first and second startup using the same data directory, confirming stable seeding behavior in this run.
✅
—
Concurrent
Four parallel SQL sessions each created and queried 20 session-scoped tables (80 total) with zero duplicate OIDs and no cross-session payload contamination, matching the expected isolation behavior for pooled ID generation.
✅
—
Format
A schema name at exactly 255 bytes remained queryable and supported create/alter/insert/drop metadata operations without ID format regression.
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.
No description provided.