Include pgvectorscale extension in pg18 images

[zh217]

Currently there is no pgvectorscale extension in pg18 images. I believe version 0.9.0 of the extension already supports pg18.

[ivanychev]

Hey @zh217 ! I actually faced exact same problem as you. Today I realized that during the first Docker run of the database it failed to bootstrap: timescale/timescaledb-docker#297

Setting TS_TUNE_MEMORY variable during the first run fixed the issue for me. Not sure how to fix existing database

EDIT: If you're running the image via Docker, try inspecting the logs for errors during the first run when DB initializes itself

[saolof]

Right, to me personally vectorscale is a more important component of the image than the timescale part. Taking a week or two to update an extension by the same company is normal. Taking a month or more is a bit weirder and makes me consider switching to a minimal image that I maintain myself

Edit: vectorscale.so is in the pg15-pg17 images but not the pg18 one, if there was a misunderstanding.

[ivanychev]

@saolof As I mentioned, it is in the image but fails to install itself during the initialization of the DB. Try looking at the logs when you start the container for the first time

[saolof]

@ivanychev This issue is about pg18 specifically, I have it working on pg17 and want to upgrade to pg18, or at least not have an image with a big version compatibility trap if a coworker wants to pg_upgrade to pg18 in the future. All images except pg18 have vectorscale in the image

[ivanychev]

@saolof I apologize, my mistake. I think I confused vectorscale with timescaledb extension. I can confirm that

docker run --rm -it \
      -e POSTGRES_PASSWORD=rootpassword \
      -e POSTGRES_USER=root \
      -e POSTGRES_DB=postgres \
      -e TS_TUNE_MEMORY=4GB \
      -p 25432:5432 \
	timescale/timescaledb-ha:pg18.1-ts2.23.1

runs without obvious errors but

CREATE EXTENSION IF NOT EXISTS vectorscale CASCADE;

fails. Vanilla pgvector is installed in the image though