chore(deps): update dependency tensorchord/vectorchord to v0.2.0#17
Merged
renovate[bot] merged 1 commit intomainfrom Feb 17, 2025
Merged
Conversation
Member
|
The name format of the debs attached to the release has changed; is each build specific to the postgres version, like the names suggest? |
Member
At that time, it was to comply with the Debian package naming convention; "-1" refers to revision 1. https://unix.stackexchange.com/questions/97289/debian-package-naming-convention |
Member
|
@xieydd @gaocegege the build is now broken because of the changed naming. Can the "Build results" job be set as required for a PR to be able to merge please? |
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.
This PR contains the following updates:
0.1.0->0.2.0Release Notes
tensorchord/VectorChord (tensorchord/VectorChord)
v0.2.0Compare Source
VectorChord 0.2 Release Notes
We are thrilled to announce the release of VectorChord 0.2, advancing vector search capabilities within PostgreSQL.
🚀 New Features
Optimized Storage Layout
Additional Data Types
Architecture Enhancements
⚡ Performance Improvements
🔧 Getting Started
📝 Summary
VectorChord 0.2 introduces support for high-dimensional vectors, Float16 data type, ARM architecture optimizations, and a more compact storage layout. These enhancements collectively improve storage efficiency and query performance, providing a superior vector retrieval experience within PostgreSQL.
What's Changed
New Contributors
Full Changelog: tensorchord/VectorChord@0.1.0...0.2.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.