Skip to content

chore(deps): update dependency tensorchord/vectorchord to v0.2.0#17

Merged
renovate[bot] merged 1 commit intomainfrom
renovate/tensorchord-vectorchord-0.x
Feb 17, 2025
Merged

chore(deps): update dependency tensorchord/vectorchord to v0.2.0#17
renovate[bot] merged 1 commit intomainfrom
renovate/tensorchord-vectorchord-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2025

This PR contains the following updates:

Package Update Change
tensorchord/VectorChord minor 0.1.0 -> 0.2.0

Release Notes

tensorchord/VectorChord (tensorchord/VectorChord)

v0.2.0

Compare 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
  • Long Cross-Page Vector Support: Redesigned internal storage allows vectors to span multiple 8KB PostgreSQL pages, enabling support for vectors with over 2000 dimensions, up to 16000 dim.
  • Enhanced Storage Efficiency: Achieves higher storage density by minimizing wasted space, reducing index size by up to 50% compared to version 0.1.
Additional Data Types
  • Float16 Support: Introduces Float16 data type, allowing users to halve the storage space required with a slight decrease in recall. Note that Float16 does not reduce the size of quantized vectors, maintaining 1 bit per dimension for original vector representation.
Architecture Enhancements
  • ARM Architecture Support: Rewritten distance calculations and Fast Scan implementations using the Scalable Vector Extension (SVE) instruction set for optimal performance on ARM-based systems.
  • AWS Graviton4 Compatibility: Leverage the latest i8g platform based on Graviton4 processors for improved performance at the same cost as i4i models.

⚡ Performance Improvements

  • Reduced Index Size: Up to 50% reduction in index size compared to version 0.1.

🔧 Getting Started

  • Comprehensive getting started guides will be available soon.

📝 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) January 27, 2025 16:34
@bo0tzz
Copy link
Member

bo0tzz commented Jan 27, 2025

The name format of the debs attached to the release has changed; is each build specific to the postgres version, like the names suggest?

Copy link
Member

@xieydd xieydd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@renovate renovate bot merged commit b37f5ef into main Feb 17, 2025
2 of 7 checks passed
@xieydd xieydd deleted the renovate/tensorchord-vectorchord-0.x branch February 17, 2025 03:14
@gaocegege
Copy link
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?

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

@bo0tzz
Copy link
Member

bo0tzz commented Feb 17, 2025

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants