Advanced visibility for PostgreSQL #3896
Merged
+439
−2
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
d6df954 to
194d169
Compare
alexshtin
approved these changes
Feb 3, 2023
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.
What changed?
Implement PostgreSQL query converter for advanced visibility.
Implement PostgreSQL
visibility_v12.go, the DB interface for advanced visibility.Why?
Support advanced visibility for PostgreSQL 12+.
How did you test it?
Existing tests.
Started local server, and ran samples with custom search attributes.
Potential risks
None, it only affects new use cases using
pluginName = postgres12.Is hotfix candidate?
No.