[Distance metrics M1] support for L2 distance #156
+296
−53
Conversation
This file contains 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
tjgreen42
changed the title
syvb
reviewed
Nov 12, 2024
cevian
requested changes
Nov 12, 2024
cevian
requested changes
Nov 13, 2024
pgrx sets CARGO_TARGET_DIR so we were previously sharing a target dir between multiple versions, which caused havoc. Now set explicitly.
cevian
reviewed
Nov 14, 2024
Co-authored-by: Matvey Arye <[email protected]> Signed-off-by: tjgreen42 <[email protected]>
Co-authored-by: Matvey Arye <[email protected]> Signed-off-by: tjgreen42 <[email protected]>
Signed-off-by: tjgreen42 <[email protected]>
The cargo environment variable is needed for correct sql generation with versioned so's. Small fixes to migration scripts. Related to work adding l2.
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.
Description
This PR adds support for distance metrics besides
cosine, beginning withL2. The primitives for this metric were already present (earlier versions ofpgvectorscaleusedL2rather than cosine), so this PR just adds the operator class-related plumbing. As discussed in the design doc (see references) we followpgvectorsyntax.Testing
DistanceTypeparameter and addedL2versions of some of the callers. We could carry this out systemically and insist that all tests have variants covering all metrics, but this seems like overkill.EXPLAIN PLANthat the correct index is still chosen.test_upgradesucceeds (with generated sql schema, not included in this PR)References