krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-05 19:08:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

Hot fix link update (#2253)

Browse Source 
* link update

* Add trailing slash

---------

Co-authored-by: Nathan LeRoy <nleroy917@users.noreply.github.com>
Co-authored-by: Abdon Pijpelink <abdon.pijpelink@qdrant.com>
This commit is contained in:
Nathan LeRoy
2026-04-02 09:26:53 +02:00
committed by GitHub
co-authored by Nathan LeRoy Abdon Pijpelink
parent 5f46ac8474
commit 110d52048c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/blog/pgvector-tradeoffs.md
+1 -1
View File
@@ -91,4 +91,4 @@ There's a reason the "start with pgvector" advice persists despite these limitat
This is a legitimate concern, and we don't want to dismiss it. However, it's also a solved problem with well-known patterns, ranging from simple dual-writes for prototypes to transactional outbox patterns for production, to full CDC pipelines for high-throughput systems.
If you've decided you need a dedicated vector store, don't let sync anxiety push you back to pgvector. Our [Postgres-Qdrant Data Synchronization guide](/documentation/data-synchronization/) walks through three progressively robust sync architectures — each with working code, failure mode analysis, and clear guidance on when to use which.
If you've decided you need a dedicated vector store, don't let sync anxiety push you back to pgvector. Our [Postgres-Qdrant Data Synchronization guide](/documentation/data-synchronization/with-postgres/) walks through three progressively robust sync architectures — each with working code, failure mode analysis, and clear guidance on when to use which.