I’ve been using this since early this year and it’s been great. It was what convinced me to just stick to Postgres rather than using a dedicated vector db.
Only working with 100m or so vectors, but for that it does the job.
pqdbr•51m ago
Are you using a dedicated pg instance for vector or you keep all your data in a single pg instance (vector and non-vector)?
ComputerGuru•43m ago
The biggest selling point to using Postgres over qdrant or whatever is that you can put all the data in the same db and use joins and ctes, foreign keys and other constraints, lower latency, get rid of effectively n+1 cases, and ensure data integrity.
dalberto•10m ago
I generally agree that one database instance is ideal, but there are other reasons why Postgres everywhere is advantageous, even across multiple instances:
- Expertise: it's just SQL for the most part
- Ecosystem: same ORM, same connection pooler
- Portability: all major clouds have managed Postgres
I'd gladly take multiple Postgres instances even if I lose cross-database joins.
throwaway7783•2m ago
Yep. If performance becomes a concern, but we still want to exploit joins etc, it's easy to set up replicas and "shard" read only use cases across replicas.
esafak•37m ago
What kind of performance do you observe with what setup?
ricw•1h ago
Only working with 100m or so vectors, but for that it does the job.
pqdbr•51m ago
ComputerGuru•43m ago
dalberto•10m ago
- Expertise: it's just SQL for the most part - Ecosystem: same ORM, same connection pooler - Portability: all major clouds have managed Postgres
I'd gladly take multiple Postgres instances even if I lose cross-database joins.
throwaway7783•2m ago
esafak•37m ago