M0: first check end to end, read-only engine and CI - #1
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Milestone M0 from ROADMAP.md. The decisions it builds on are recorded there (2026-09-25).
checks/<id>/. A broken check fails the build with its file and line, as does SQL that calls a function aREAD ONLYtransaction doesn't stop, or one that runs SQL from a string.BEGIN TRANSACTION READ ONLYwithSET LOCALstatement and lock timeouts andsearch_path = pg_catalog, pg_temp, then rolls back. Nothing is set for the whole session, so nothing leaks through a transaction pooler.replication-slot-inactivehas fires and healthy fixtures on Postgres 14 to 18. Each fixture gets a fresh Testcontainers Postgres, and the check runs as a role with onlypg_monitor.pgcheckup scanprints the terminal report and exits 0, 1 or 2.pgcheckup listlists the checks. Connections come from apostgres://URL, a libpq key-value string or thePG*variables. Errors never repeat the input.--fail-on warning.