fix(pgvector): add skipInitializationCheck option to disable schema c… #8414
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.
This PR introduces a new
skipInitializationCheck
option inPgVectorStore
, allowing users to disable automatic schema modification during initialization (i.e.,CREATE EXTENSION
andCREATE TABLE
).This improves compatibility with production environments where database credentials are restricted and schema-altering permissions are not granted (e.g., cloud deployments following the principle of least privilege).
Changes:
skipInitializationCheck
option toPgVectorStore
ensureTableInDatabase
logic if the flag is enabledFixes #8401