From 110d52048c7e7490ba2e7dbd982c54d122a853be Mon Sep 17 00:00:00 2001 From: Nathan LeRoy <41063083+nleroy917@users.noreply.github.com> Date: Thu, 2 Apr 2026 03:26:53 -0400 Subject: [PATCH] Hot fix link update (#2253) * link update * Add trailing slash --------- Co-authored-by: Nathan LeRoy Co-authored-by: Abdon Pijpelink --- qdrant-landing/content/blog/pgvector-tradeoffs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/blog/pgvector-tradeoffs.md b/qdrant-landing/content/blog/pgvector-tradeoffs.md index 87c343ba5..ff980dd02 100644 --- a/qdrant-landing/content/blog/pgvector-tradeoffs.md +++ b/qdrant-landing/content/blog/pgvector-tradeoffs.md @@ -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. \ No newline at end of file +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. \ No newline at end of file