Add CNC-owned scoped PostgreSQL introspection - #1719
Draft
Zetazzz wants to merge 1 commit into
Draft
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.
Stack
Base:
test/performance-harness-coreArchitecture boundary
This PR implements schema-scoped PostgreSQL introspection entirely on the CNC side.
ConstructivePgIntrospectionPluginis a replacement built from the publicPgIntrospectionPluginexport.ScopedIntrospectionPresetdisables the upstream plugin and installs the replacement atomically.ConstructivePresetopts into that preset explicitly.The only pnpm patches are:
pg-introspection@1.0.1: parameterized scoped query generation and direct range lookup.@dataplan/pg@1.1.1: exact introspection-client destruction support.There is deliberately no
graphile-build-pgpatch and no build-state retirement behavior in this PR.Lifecycle and safety
About 178 lines (including local boundary comments) mirror/rewrite upstream private gather/cache flow because the public plugin does not expose that control surface. This is intentionally isolated in one file so it can be deleted when upstream progressive introspection is available.
Harness extension
Extends #1716 with fresh-process
stockandscopedcases without loadingConstructivePreset. It preserves schema-hash, runtime-validation, PID, lifecycle and secret-redaction output contracts.Validation
graphile-settings: 12 suites / 112 tests passed.@constructive-io/perf-harness: 6 suites / 8 tests passed.graphile-settings.git diff --checkpassed.pnpm install --frozen-lockfile --offlinepassed.90201,902023b9dab5243611a57da1c0721ea3bc1aba455051124e43549e3c326178b3e97c1Upstream migration
This is a CNC-owned interim implementation. Once Graphile progressive introspection provides equivalent behavior, remove the replacement plugin and the two scoped-introspection patches while keeping the harness as the migration/equivalence gate.