On Fri, Mar 4, 2022 at 10:22:11PM +0530, Atri Sharma wrote:
> TF/IDF should be pretty simple to implement IMO.
>
> And no, Solr does not give preference to prior documents.
>
> However, Solr allows you to "boost" specific terms, thus creating the
> impression of preference.
Postgres can do th
TF/IDF should be pretty simple to implement IMO.
And no, Solr does not give preference to prior documents.
However, Solr allows you to "boost" specific terms, thus creating the
impression of preference.
On Fri, 4 Mar 2022, 22:15 Bruce Momjian, wrote:
> On Fri, Mar 4, 2022 at 11:43:57AM -0500,
On Fri, Mar 4, 2022 at 11:43:57AM -0500, Tom Lane wrote:
> "Bayer, Samuel" writes:
> > One concrete question, I suppose, is: the classic TF/IDF search strategy
> > relies on inverse document frequency, which looks across the corpus. I
> > can't tell whether that corpus-wide frequency informatio
On Fri, Mar 4, 2022 at 11:39:39AM -0500, Bayer, Samuel wrote:
> I've tried both ranking functions. I've tried a variety of the
> normalization settings. I'm using the standard English language
> configuration. Postgres 13.
>
> I do understand your FTS philosophy - I suppose I'm looking for
> guidan
"Bayer, Samuel" writes:
> One concrete question, I suppose, is: the classic TF/IDF search strategy
> relies on inverse document frequency, which looks across the corpus. I can't
> tell whether that corpus-wide frequency information is taken into account in
> either ranking function.
The docume
I've tried both ranking functions. I've tried a variety of the normalization
settings. I'm using the standard English language configuration. Postgres 13.
I do understand your FTS philosophy - I suppose I'm looking for guidance about
how best to approximate the search capability in Solr using t
Bruce Momjian writes:
> On Fri, Mar 4, 2022 at 10:41:16AM -0500, Bayer, Samuel wrote:
>> I apologize for not being able to be more specific.
> I know it is hard to quantify. Is it possible that Postgres is treating
> all the terms equally, while Solr is prioritizing terms that are earlier
> in t
On Fri, Mar 4, 2022 at 10:41:16AM -0500, Bayer, Samuel wrote:
> Example anecdote: the documents I'm searching come with metadata
> (e.g., title), which I'm not indexing specially (not a separate field,
> just part of the raw text of the document). When I search even for
> single terms, and look at
Fair question. Not worried so much about speed. Looking, essentially, at
precision by rank (i.e., average precision and variants). I have not explored
the contrasts between the default English language configuration in Postgres
and the one in Solr - I have no reason to believe that there's anyt
Can you define what "high quality" is?
Are you referring to precision? Or recall? Or speed? Or query dialect?
On Fri, Mar 4, 2022 at 8:59 PM Bayer, Samuel wrote:
>
> Thanks for replying. My problem is that I can't provide enough guidance on
> what isn't working, because (a) I don't have good en
Thanks for replying. My problem is that I can't provide enough guidance on what
isn't working, because (a) I don't have good enough intuitions about how the
normalization options are expected to affect the results, and (b) I can't
identify a specific missing function - I'm just observing that I
On Fri, Mar 4, 2022 at 08:10:48AM -0500, Bayer, Samuel wrote:
> Hi all -
>
> When I have a need for both sophisticated database querying and
> full-text search, I'd rather not stand up a technology stack with
> multiple tools (e.g., Postgres and Apache Solr, or Postgres and
> ElasticSearch with a z
Hi all -
When I have a need for both sophisticated database querying and full-text
search, I'd rather not stand up a technology stack with multiple tools (e.g.,
Postgres and Apache Solr, or Postgres and ElasticSearch with a zomboDB bridge).
So I've been looking at the Postgres full-text search
13 matches
Mail list logo
