[New Extension]: VectorChord (vchord)

[xieydd]

Is there an existing issue for this extension request?

• I have searched for an existing issue, and could not find a duplicate request.

Extension Name

vchord

Project Repository URL

https://github.com/tensorchord/VectorChord

Extension Website URL (Optional)

https://vectorchord.ai/

Short Description

VectorChord (vchord) is a PostgreSQL extension engineered for scalable, high-performance, and cost-effective vector search.

Main LICENSE Link

https://github.com/tensorchord/VectorChord/blob/main/LICENSE

License Compliance

• The extension's license (linked above) complies with the list of allowed licenses.

Known Dependent Extensions

pgvector

Component Owner and Maintenance Commitment

• I/My organization commit to becoming the Component Owner and maintaining the extension image in the future.

Additional Notes (Optional)

VectorChord uses a dual licence model AGPL-3.0-only or Elastic License v2. Neither licence is included in the CNCF Allowed Third-Party Licence Policy list. License Compliance is a required checkbox, so I temporarily checked it. This extension is written in Rust using the pgrx framework. The build requires the Rust toolchain, cargo-pgrx ,and clang as build-time dependencies. No additional OS-level runtime dependencies are needed.

GitHub Handles of Component Owners

@xieydd

Code of Conduct

• I agree to follow this project's Code of Conduct

[gbartolini]

Hi @xieydd,

I wanted to update you regarding the licensing. I am currently awaiting feedback from the CNCF legal team. Given that these are redistributable artefacts and that the license terms only apply to the specific extension image, I believe we can be flexible with the requirements. This means we could include licenses approved by the Free Software Foundation (like we do for PostGIS), such as the GNU Affero GPL 3. I will let you know about this.

As for the building process, maintenance responsibility will ultimately fall to you. We generally prefer to use PGDG packages because they are rigorously tested against the corresponding Postgres packages. While we could consider exceptions, I need to wait for input from other maintainers.

Thank you,
Gabriele

[xieydd]

Hi @gbartolini , thank you for the detailed explanation. I will submit a PR as soon as possible and await your and the other maintainers' input.