https://github.com/chkpwd/cdpgvecto.rs

PostgreSQL Image with vecto.rs support based on CrunchyData Postgres images.
https://github.com/chkpwd/cdpgvecto.rs

crunchydata docker kubernetes postgresql vector-database

Last synced: 3 months ago
JSON representation

PostgreSQL Image with vecto.rs support based on CrunchyData Postgres images.

• Host: GitHub
• URL: https://github.com/chkpwd/cdpgvecto.rs
• Owner: chkpwd
• License: apache-2.0
• Created: 2023-12-16T12:23:34.000Z (11 months ago)
• Default Branch: main
• Last Pushed: 2023-12-17T10:00:46.000Z (11 months ago)
• Last Synced: 2023-12-17T13:53:48.178Z (11 months ago)
• Topics: crunchydata, docker, kubernetes, postgresql, vector-database
• Language: Dockerfile
• Homepage:
• Size: 15.6 KB
• Stars: 1
• Watchers: 1
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# CrunchyData PGO with pgvecto.rs Extension

This repository contains container images for [CrunchyData PGO](https://github.com/CrunchyData/postgres-operator) that include the [pgvecto.rs](https://github.com/tensorchord/pgvecto.rs) extension.

## Important Configuration Note

> :warning: **If you are deploying this image on an existing database:** The postgres configuration must be updated to enable the pgvecto.rs extension. 

To enable the extension, you need to set the `shared_preload_libraries` and `search_path` in your Cluster spec. Add the following configuration to your `PostgresCluster` yaml file:

```yaml

apiVersion: postgres-operator.crunchydata.com/v1beta1

kind: PostgresCluster

spec:

  ...

  patroni:

    dynamicConfiguration:

      postgresql:

        synchronous_commit: "on"

        parameters:

          shared_preload_libraries: "vectors.so"

          search_path: '"$user", public, vectors'

```

> :warning: If you want to do a major Postgres version upgrade like described in the [official docs](https://access.crunchydata.com/documentation/postgres-operator/latest/guides/major-postgres-version-upgrade), make sure you do the following steps or the upgrade will fail:

1. Connect to the database where you have enabled the `vectors` extension and disable it with `DROP EXTENSION vectors;`.

2. Remove the `dynamicConfiguration` block you added to `PostgresCluster` from above.

3. Follow the upgrade instruction from the official doc.

4. Add back the `dynamicConfiguration` block and enable the extension in the database again with `CREATE EXTENSION vectors;`