Adding support for `VECTOR(1536)` for Postgres/pgvector
BarnabyShearer opened this issue · comments
Search before asking
- I searched the issues and found no similar issues.
Description
I note that PostGIS types are supported. I understand its popularity, and that are too many Postgres extensions to support them all. However, https://github.com/pgvector/pgvector is understandably popular at the moment and nearly always uses VECTOR(1536)
which is currently unpassable. I wonder what this project's policy is on adding support for further extensions?
I also wonder if an alternative approach might be more powerful; a config setting with a set of types which should be bracketed?
Use case
CREATE TABLE search (
embedding VECTOR(1536)
);
Dialect
Postgres for people using the https://github.com/pgvector/pgvector extension.
Are you willing to work on and submit a PR to address the issue?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct