Related discussion for pgvector perf: https://news.ycombinator.com/item?id=45798479
the main issue with pgvectorscale is that it's not available in RDS :(
Postgres extension complements pgvector for performance and scale
11–20 of 26 posts
Re: Postgres extension complements pgvector for performance and scale
#12This is still unsupported in RDS, right?
correct afaik :(
Re: Postgres extension complements pgvector for performance and scale
#13Related discussion for pgvector perf: https://news.ycombinator.com/item?id=45798479
the main issue with pgvectorscale is that it's not available in RDS :(
Yes, RDS seems to really hold PG back on AWS, with all the interesting pg extensions getting released now (pg_lake). It is a share I can't move to other PG vendors because it is a pain in the ass to get all privacy, legal docs in order.
Re: Postgres extension complements pgvector for performance and scale
#14Combined with our other search extension for full text search these two extensions make postgres a really capable hybrid search engine: https://github.com/timescale/pg_textsearch
Re: Postgres extension complements pgvector for performance and scale
#15This is still unsupported in RDS, right?
We have a lot of happy customers that moved from rds to tiger cloud if you think pgvectorscale is interesting to you and you don't want to self host pg.
But yes big cloud providers move slow in adopting extensions.
Re: Postgres extension complements pgvector for performance and scale
#16I’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.
What kind of performance do you observe with what setup?
Depends on the query and I don’t have exact numbers of the top of my head, but we’re talking low 100ms range for something pgvector itself wasn’t able to handle in a reasonable amount of time.
Re: Postgres extension complements pgvector for performance and scale
#17I’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.
Are you using a dedicated pg instance for vector or you keep all your data in a single pg instance (vector and non-vector)?
All in one of course. That’s the biggest advantage. And why postgres is great - it covers virtually all standard use cases.
Re: Postgres extension complements pgvector for performance and scale
#18Earlier quoted context omitted.
the main issue with pgvectorscale is that it's not available in RDS :(
Yes, RDS seems to really hold PG back on AWS, with all the interesting pg extensions getting released now (pg_lake). It is a share I can't move to other PG vendors because it is a pain in the ass to get all privacy, legal docs in order.
Yes, the InfoSec advantages of using RDS are very real, especially in B2B Enterprise SaaS.
Re: Postgres extension complements pgvector for performance and scale
#19Related discussion for pgvector perf: https://news.ycombinator.com/item?id=45798479
the main issue with pgvectorscale is that it's not available in RDS :(
I'm considering hosting a separate pg db just to be able to access certain extensions. I am interested in this extension as well as https://wiki.postgresql.org/wiki/Incremental_View_Maintenanc... (also not available on RDS). Then use logical replication for specific data source tables (guess it would need to be DMS).
Re: Postgres extension complements pgvector for performance and scale
#20Combined with our other search extension for full text search these two extensions make postgres a really capable hybrid search engine: https://github.com/timescale/pg_textsearch
I'm not how you'd combine the two; care to give us a quick outline ?