Skip to content

Commit 2d7377a

Browse files
authored
fix(docs): mention DB_VECTOR_EXTENSION env in pgvector->vchord migration guide (#18508)
mention `DB_VECTOR_EXTENSION` env in pgvector->vchord migration guide
1 parent 8fcf47e commit 2d7377a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/docs/administration/postgres-standalone.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,8 @@ ALTER TABLE face_search ALTER COLUMN embedding SET DATA TYPE vector(512);
128128
1. Ensure you have at least 0.7.0 of pgvector installed. If it is below that, please upgrade it and run the SQL command `ALTER EXTENSION vector UPDATE;` using psql or your choice of database client
129129
2. Follow the Prerequisites to install VectorChord
130130
3. If Immich does not have superuser permissions, run the SQL command `CREATE EXTENSION vchord CASCADE;`
131-
4. Start Immich and let it create new indices using VectorChord
131+
4. Remove the `DB_VECTOR_EXTENSION=pgvector` environmental variable as it will make Immich still use pgvector if set
132+
5. Start Immich and let it create new indices using VectorChord
132133

133134
Note that VectorChord itself uses pgvector types, so you should not uninstall pgvector after following these steps.
134135

0 commit comments

Comments
 (0)