Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add support to pgvector #253

Open
mhordynski opened this issue Dec 17, 2024 · 0 comments · May be fixed by #267
Open

feat: add support to pgvector #253

mhordynski opened this issue Dec 17, 2024 · 0 comments · May be fixed by #267
Assignees
Labels
feature New feature or request priority Top priority issue
Milestone

Comments

@mhordynski
Copy link
Member

Feature description

The goal of this issue is to add a new VectorStore that utilizes pgvector, an extension for PostgreSQL, to store its vectors.

By default, the metadata for the entries should be stored alongside the vectors in the same PostgreSQL table.

Motivation

Many applications opt for pgvector because they are already using PostgreSQL as their relational database. Additionally, pgvector is offered as a managed database by all major cloud providers.

Additional context

No response

@mhordynski mhordynski added the feature New feature or request label Dec 17, 2024
@mhordynski mhordynski moved this to Backlog in ragbits Dec 17, 2024
@mhordynski mhordynski moved this from Backlog to Ready in ragbits Dec 17, 2024
@kzamlynska kzamlynska self-assigned this Dec 20, 2024
@ludwiktrammer ludwiktrammer added this to the Ragbits 0.7 milestone Jan 2, 2025
@ludwiktrammer ludwiktrammer moved this from Ready to In review in ragbits Jan 8, 2025
@micpst micpst linked a pull request Jan 8, 2025 that will close this issue
@ludwiktrammer ludwiktrammer added the priority Top priority issue label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request priority Top priority issue
Projects
Status: In review
Development

Successfully merging a pull request may close this issue.

3 participants