You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m using wolfi-base to build a PostgreSQL database image and need to include both PostGIS and pgVector. However, I’ve encountered an issue: the postgis package is available only for PostgreSQL v17, while pgvector is available only for PostgreSQL v16. I’ve submitted a request for a PostgreSQL v17-compatible version of pgvector, but in the meantime, does anyone have suggestions or workarounds to get pgvector running in my PostgreSQL 17 setup?
Would building pgvector from source be a viable approach, or are there alternative solutions I should consider? If building from source in the Dockerfile are the suggestion as to what packages are needed for that? Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I’m using wolfi-base to build a PostgreSQL database image and need to include both PostGIS and pgVector. However, I’ve encountered an issue: the postgis package is available only for PostgreSQL v17, while pgvector is available only for PostgreSQL v16. I’ve submitted a request for a PostgreSQL v17-compatible version of pgvector, but in the meantime, does anyone have suggestions or workarounds to get pgvector running in my PostgreSQL 17 setup?
Would building pgvector from source be a viable approach, or are there alternative solutions I should consider? If building from source in the Dockerfile are the suggestion as to what packages are needed for that? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions