<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data Synchronization on Qdrant - Vector Search Engine</title><link>https://qdrant.tech/documentation/data-synchronization/</link><description>Recent content in Data Synchronization on Qdrant - Vector Search Engine</description><generator>Hugo</generator><language>en-us</language><managingEditor>info@qdrant.tech (Andrey Vasnetsov)</managingEditor><webMaster>info@qdrant.tech (Andrey Vasnetsov)</webMaster><atom:link href="https://qdrant.tech/documentation/data-synchronization/index.xml" rel="self" type="application/rss+xml"/><item><title>With Postgres</title><link>https://qdrant.tech/documentation/data-synchronization/with-postgres/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><author>info@qdrant.tech (Andrey Vasnetsov)</author><guid>https://qdrant.tech/documentation/data-synchronization/with-postgres/</guid><description>&lt;h1 id="keeping-postgres-and-qdrant-in-sync">Keeping Postgres and Qdrant in Sync&lt;/h1>
&lt;p>If you&amp;rsquo;ve migrated your vectors to Qdrant but still use Postgres as your source of truth, the next challenge is keeping both systems in sync as data changes.&lt;/p>
&lt;p>This guide covers three progressively robust sync architectures — from simple application-level dual-writes to production-grade Change Data Capture — with working code, failure mode analysis, and clear guidance on when to use each.&lt;/p>
&lt;p>Not sure if you need a dedicated vector store alongside Postgres? Read our &lt;a href="https://qdrant.tech/blog/pgvector-tradeoffs/">pgvector tradeoffs blog post&lt;/a> to understand the six conditions under which pgvector is sufficient — and when you&amp;rsquo;ll outgrow it.&lt;/p></description></item></channel></rss>