Update apps/www/_blog/2023-07-13-pgvector-performance.mdx

Co-authored-by: Copple <[email protected]>
ssi379 · Jul 13, 2023 · 8f94e88 · 8f94e88
1 parent 5913a61
commit 8f94e88
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/apps/www/_blog/2023-07-13-pgvector-performance.mdx b/apps/www/_blog/2023-07-13-pgvector-performance.mdx
@@ -167,7 +167,7 @@ The Qdrant benchmark uses “default” configuration and is in not indicative o
   />
 </div>
 
-Although more compute is required to match Qdrant's precision and RPS levels concurrently, this is still a satisfying outcome. It means that it's not a _necessity_ to use another vector database - if you want to lower your operational complexity, just increase your Postgres size.
+Although more compute is required to match Qdrant's precision and RPS levels concurrently, this is still a satisfying outcome. It means that it's not a _necessity_ to use another vector database. You can put everything in Postgres to lower your operational complexity.
 
 ### Final results: pgvector performance