The store keeps the vector extension the predecessor's database had #41

2026-09-22T21:30:29Z

jschoubben commented

2026-09-22 21:30:29 +00:00

The postgres module pinned a plain image. The database it replaces on the control-node runs the pgvector build, and the extension is a requirement, so moving data into a store without it would lose a capability the machine had — silently, until something asked for a vector column.

Same major version, so the data directory is unchanged and the container is simply recreated: pgvector/pgvector for Postgres 17, pinned by digest.

Checked: the controller's catalogue tests parse and resolve these manifests.

The postgres module pinned a plain image. The database it replaces on the control-node runs the pgvector build, and the extension is a requirement, so moving data into a store without it would lose a capability the machine had — silently, until something asked for a vector column. Same major version, so the data directory is unchanged and the container is simply recreated: `pgvector/pgvector` for Postgres 17, pinned by digest. Checked: the controller's catalogue tests parse and resolve these manifests.

jschoubben added 1 commit 2026-09-22 21:30:29 +00:00

Keep the vector extension the predecessor's database had: the store runs the pgvector build of the same major 5eb1baf5fe

jschoubben merged commit 4f4a0750de into main

2026-09-22 21:30:34 +00:00

jschoubben deleted branch fix/store-keeps-pgvector

2026-09-22 21:30:34 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#41