From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Sv: Replacing Apache Solr with Postgre Full Text Search? |
Date: | 2020-03-26 15:32:58 |
Message-ID: | VisenaEmail.11.aa92121a17c2d874.1711773f1e6@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På onsdag 25. mars 2020 kl. 13:36:38, skrev J2eeInside J2eeInside <
j2eeinside(at)gmail(dot)com <mailto:j2eeinside(at)gmail(dot)com>>:
Hi all,
I hope someone can help/suggest:
I'm currently maintaining a project that uses Apache Solr /Lucene. To be
honest, I wold like to replace Solr with Postgre Full Text Search. However,
there is a huge amount of documents involved - arround 200GB. Wondering, can
Postgre handle this efficiently?
Does anyone have specific experience, and what should the infrastructure look
like?
P.S. Not to be confused, the Sol works just fine, i just wanted to eliminate
one component from the whole system (if Full text search can replace Solr at
all)
I see you've gotten some answers but wanted to chime in...
We seach in ~15mill. emails and ~10 mill documents (extracted text from
Word/PDF etc. using Java-tools), and use PG and FTS (gin, not rum) for the
exact same reasons as Evergreen (it seems). We have to mix FTS with
domain-specific logic/filtering and that is based on relational data in the
database. I don't see how we could have done that using an external
search-engine. Maybe it's easy, I don't have any experience with it.
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | J2eeInside J2eeInside | 2020-03-26 16:05:27 | Re: Replacing Apache Solr with Postgre Full Text Search? |
Previous Message | Mike Rylander | 2020-03-26 15:18:16 | Re: Replacing Apache Solr with Postgre Full Text Search? |