https://github.com/oelmekki/postgres-350d

Docker build of postgresql changing the dimension limit for the cube extension, raising it to 350
https://github.com/oelmekki/postgres-350d

machine-learning postgres postgresql vector-database

Last synced: about 1 month ago
JSON representation

Docker build of postgresql changing the dimension limit for the cube extension, raising it to 350

• Host: GitHub
• URL: https://github.com/oelmekki/postgres-350d
• Owner: oelmekki
• License: other
• Created: 2016-10-09T18:36:34.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2023-10-06T11:36:15.000Z (over 1 year ago)
• Last Synced: 2023-10-06T12:34:33.142Z (over 1 year ago)
• Topics: machine-learning, postgres, postgresql, vector-database
• Language: Dockerfile
• Homepage:
• Size: 7.81 KB
• Stars: 17
• Watchers: 3
• Forks: 10
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# pg350d

Docker build of postgresql-15.3 changing the dimension limit for the cube

extension, raising it to 350.

This is needed to be able to work with words embedding or other machine

learning related vectors with postgres.

> Note: since pg350d was released, there has been some efforts to support

> machine learning friendly vectors in [pgvector](https://github.com/pgvector/pgvector),

> which supports up to 16k dimensions.

You can easily generate a build for your own need in term of dimensions by

editing this dockerfile.

## What is the problem again?

The cube extension, which you'll use to perform operations on vectors, has

a hard limit of 100 dimensions per vector.

## Download

A built image is available on Gitlab's registry. You can pull it this way:

```

docker pull registry.gitlab.com/oelmekki/postgres-350d:15.3

```

## Is it safe?

Patching the hardcoded limit is [the recommended way in postgres

doc](https://www.postgresql.org/docs/current/cube.html#id-1.11.7.20.9).

I've been using it for a few years in production, and didn't encounter any

problem.

## How to raise postgresql's cube extension dimensions limit?

Even if you're not familiar with docker, reading the Dockerfile from this repos

should be easy enough to teach you how to do it yourself. Spoiler:

* sources are in the `contrib/cube/` directory from postgres sources

* limit is in `contrib/cube/cubedata.h`

* make and make install should be ran with the `USE_PGXS=true` env variable