pgvector install 404s: pinned deb version 0.8.1-2 no longer exists in pgdg pool

[vasconceloscezar]

autopg downloads pgvector from a hardcoded version:

https://apt.postgresql.org/pub/repos/apt/pool/main/p/pgvector/postgresql-${pgMajor}-pgvector_0.8.1-2.pgdg+1_${arch}.deb

pgdg removed 0.8.1-2 from the pool (current: 0.8.5/0.8.6), so every install with runtime.enablePgvector=true logs Failed to install pgvector extension files (non-fatal) — Download failed: 404 and downstream consumers (khal/brain personal deploy) die at CREATE EXTENSION vector.

Repro: fresh autopg v3.0.7, autopg config set runtime.enablePgvector true, start postmaster → 404 warn, pg_available_extensions has no vector.

Suggestion: resolve the latest available version from the pool index (or at least try a list of known versions) instead of pinning one, since pgdg garbage-collects old debs.

Workaround we applied: manual download of 0.8.6-1, copied vector.so + extension SQLs into the runtime dirs and wrote a matching vector.meta.json so auto-heal doesn't remove them.

[automagik-genie]

Root cause: _installPgvectorFromDeb in src/postgres.js built the download URL from a hard-coded 0.8.1-2, and pgdg garbage-collects superseded packages from its pool, so the URL 404'd as soon as 0.8.5/0.8.6 replaced it. The 404 was swallowed as a non-fatal warning, leaving the postmaster up with no vector extension for CREATE EXTENSION to find.

Fix in #147: the version is now resolved from the pool directory listing (highest wins, rest kept as retries), with AUTOPG_PGVECTOR_VERSION=<ver> to pin and AUTOPG_PGVECTOR_DEB=<file> to install a local .deb without network (the workaround you applied by hand). The resolved version lands in vector.meta.json, and the warning now lists the versions tried plus the override to use.