-
Notifications
You must be signed in to change notification settings - Fork 64
Add pgvector extension test #1205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add this test to:
percona-postgresql-operator/e2e-tests/run-minikube.csv
percona-postgresql-operator/e2e-tests/run-pr.csv
percona-postgresql-operator/e2e-tests/run-release.csv
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have an e2e for custom extensions which implies that all the custom extensions will be added there. Should we approach the build-in extensions e2e test in a similar way? Just wondering to understand how we think future tests will be added.
e2e-tests/tests/pgvector-extension/02-verify-pgvector-extension-is-enabled.yaml
Outdated
Show resolved
Hide resolved
Hi @gkech ,
We have discussed this and decided that built-in extension will their own separate tests. Bc some of them may require other components like pmm, others can be long running (expect this with TDE). |
commit: 14d0021 |
CHANGE DESCRIPTION
Problem:
Add tests to verify pgvector extension.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
Config/Logging/Testability