bo0tzz / cnpgvecto.rs Goto Github PK

Container images for cloudnative-pg with the pgvecto.rs extension installed

License: Apache License 2.0

Dockerfile 100.00%

cloudnative-pg cloudnativepg container-images postgres postgresql cnpg pgvecto-rs

cnpgvecto.rs's Introduction

Note

This repository has been archived in favour of https://github.com/tensorchord/cloudnative-pgvecto.rs.
You can safely continue using the images from this repository until you need to upgrade to a new pgvecto.rs version.

cnpgvecto.rs

Container images for cloudnative-pg with the pgvecto.rs extension installed.

Important

If you are using this image on an existing database, the postgres configuration needs to be altered to enable the extension. You can do this by setting shared_preload_libraries in your Cluster spec:

apiVersion: postgresql.cnpg.io/v1
kind: Cluster
spec:
  (...)
  postgresql:
    shared_preload_libraries:
      - "vectors.so"

cnpgvecto.rs's People

Contributors

Stargazers

Watchers

Forkers

imtoanle

cnpgvecto.rs's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

dockerfile

Dockerfile

github-actions

.github/workflows/docker.yml

actions/checkout v4

mikefarah/yq v4.40.5

actions/checkout v4

docker/setup-qemu-action v3.0.0

docker/setup-buildx-action v3.0.0

docker/login-action v3.0.0

tj-actions/changed-files v41

actions/github-script v7

docker/metadata-action v5

docker/build-push-action v5.1.0

regex

versions.yaml

ghcr.io/cloudnative-pg/postgresql 14.10

ghcr.io/cloudnative-pg/postgresql 15.5

ghcr.io/cloudnative-pg/postgresql 16.1

tensorchord/pgvecto.rs v0.1.13

Check this box to trigger a request for Renovate to run again on this repository

Create Dockerfile for container build

Tbd:

Do we build FROM https://github.com/cloudnative-pg/postgres-containers or fork it?
Do we build pgvecto.rs in a builder stage, or beforehand (outside of docker) in github actions?

The Dockerfile should probably take the postgres/pgvecto.rs/etc version as build args.

permission denied to create extension "vectors"

I think this is just a database role permissions thing, but if there's anything that can be done to automatically load this from the container image side that would be great.

Builds for postgres 12/13

This would require building pgvectors from source (or getting them to publish debs for those versions). TBD if support for these versions is actually needed.

Extension is not loadable without restart of Postgres cluster

It appears that the extension doesn't load without needing a restart of cnpg, it should probably be automated somehow.

Limit pushing of release tags

Currently the release tags are pushed on every PR and every commit on main. They should only be pushed when a release is actually desired.

Create github actions workflow for building containers

https://github.com/bo0tzz/pgvector-images/blob/main/.github/workflows/docker.yml can be a basis.

Tbd: How do we manage all the tags with nice minor versions and such? (docker/metadata-action might be able to handle this nicely.)

Work out tagging/versioning scheme

Some options:

Directly copy the (postgres version) tags from the cnpg images: 15, 16, 16.1, etc., always with the latest pgvecto.rs version (at build time).
Include the pgvecto.rs version in the tags: 15-v0.1.8, 16.1-v0.1.7, etc.
???
Both?

Upgrade postgres/pgvecto.rs versions with Renovate

The versions are (currently) defined in the github actions workflow: https://github.com/bo0tzz/cnpgvecto.rs/blob/main/.github/workflows/docker.yml#L27-L32. It would be great if renovate could PR updates for these.