Repository navigation
Conversation
- Add absolute PG0_HOME and PG0_INSTALLATION_DIR overrides without changing defaults. - Honor PG0_EXECUTABLE before bundled Python SDK binary discovery. - Document Windows provisioning and test SDK path isolation with pgvector and restart.
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.
On Windows machines with application-control policies, the Python SDK always prefers the executable inside its wheel, and the CLI always extracts PostgreSQL into the user's profile. An approved executable directory cannot currently be selected independently of writable database state.
This adds three optional environment variables:
PG0_EXECUTABLE: absolute path to an existing pg0 executable; takes precedence over the Python wheel's bundled executable.PG0_INSTALLATION_DIR: absolute root for extracted PostgreSQL and extension files, keeping the existing version subdirectory layout.PG0_HOME: absolute root for instance metadata and default data directories, used consistently by all commands.Defaults and SDK method signatures are unchanged. Invalid overrides fail explicitly instead of falling back to a different location. The README documents provisioning, read/execute access on Windows after initial extraction, and the distinction from the build-time
PG0_BINARY_PATHsetting.Validation:
vector.dllloaded from the configured installation outside the user profile. The installation was given read/execute-only ACLs during the Hindsight test; no symbolic links were used and native-file hashes remained unchanged.The target organization's application-control rules still need to permit the chosen executable paths; this change only makes those paths configurable.