From 2d7377a5e90dac3b33ac1bd3e446a20264c75e3c Mon Sep 17 00:00:00 2001
From: Mert <101130780+mertalev@users.noreply.github.com>
Date: Thu, 22 May 2025 22:43:28 -0400
Subject: [PATCH] fix(docs): mention `DB_VECTOR_EXTENSION` env in
 pgvector->vchord migration guide (#18508)

mention `DB_VECTOR_EXTENSION` env in pgvector->vchord migration guide
---
 docs/docs/administration/postgres-standalone.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/docs/administration/postgres-standalone.md b/docs/docs/administration/postgres-standalone.md
index 95a281d0e1..9f0776a363 100644
--- a/docs/docs/administration/postgres-standalone.md
+++ b/docs/docs/administration/postgres-standalone.md
@@ -128,7 +128,8 @@ ALTER TABLE face_search ALTER COLUMN embedding SET DATA TYPE vector(512);
 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
 2. Follow the Prerequisites to install VectorChord
 3. If Immich does not have superuser permissions, run the SQL command `CREATE EXTENSION vchord CASCADE;`
-4. Start Immich and let it create new indices using VectorChord
+4. Remove the `DB_VECTOR_EXTENSION=pgvector` environmental variable as it will make Immich still use pgvector if set
+5. Start Immich and let it create new indices using VectorChord
 
 Note that VectorChord itself uses pgvector types, so you should not uninstall pgvector after following these steps.