In general when evaluating a new option for my search engine, I like to take a set of queries that represent my users, with some head, and some tail queries. Rate the results that you are getting, to get a concrete numbers on the quality of search. Then, take that rated “judgement set” and point the same queries at your Postgres based search, and compare the differences that you are getting!
There are a number of tools out there, though you can script it yourself too. https://quepid.com/ is one that I’m involved with ;-). > On Mar 4, 2022, at 9:32 AM, Bayer, Samuel <s...@mitre.org> wrote: > > Hi all - > > In the interest of reducing my technology stack, I'm exploring whether using > Postgres full-text search instead of Solr might be an option when I need both > complex querying and full-text search. In my experience, so far, Postgres > can't compare to Solr, but I'm trying to understand why, in order to have > more of an ability to evaluate the functionality/complexity tradeoffs. I know > something about search technologies, but I'm not an expert by any stretch of > the imagination, and I've been looking for sources that talk about the > comparison in an informed way - people, blogs, articles. So far, everything > I've found is extremely basic. Does anyone have any pointers for me? > > Thanks in advance - > Sam Bayer > The MITRE Corporation > s...@mitre.org _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
