Awesome project! It would be interesting to see performance tests. I know that a scientific experiment is very difficult, so approximate numbers are enough. Anyway, thanks for your work :)
Show HN: Retake – Open-Source Hybrid Search for Postgres
21–24 of 24 posts
Re: Show HN: Retake – Open-Source Hybrid Search for Postgres
#22Thanks for sharing; this project looks very promising! What precipitated your fork of pgsync and how do you foresee maintaining compatibility with that project?
Thanks, appreciate it!
We forked pgsync for the silly reason that they hadn't published to PyPi in months, and some of their dependencies were out of date. We haven't made any modifications to pgsync so maintaining compatibility shouldn't be an issue, and we'll likely revert back to the main library once their dependencies are brought up to speed.
Re: Show HN: Retake – Open-Source Hybrid Search for Postgres
#23I would like something that can keep postgres (or other source of truth) in sync with existing search database (like Elastic, Meili, or Qdrant).
But the catch is that it's rare that there's 1:1 mapping between the source of truth and what is indexed. The simplest example would be: You have a document table, but you actually index document chunks.
Therefore I would like something that accepts a preprocessing function and keeps the search data in sync when the source changes. Ideally, it should not reinvent full-text / vector based search and plug in with existing solutions.
Re: Show HN: Retake – Open-Source Hybrid Search for Postgres
#24Can’t you just use OpenSearch? What is the point of going through Postgres when you already have OpenSearch?