Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds - Mailing list pgsql-general

From Ninad Shah
Subject Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds
Date
Msg-id CAOFEiBd1Vi_bZTLh81RTCBPODnfr_7R8Dv-fzLhCcSZAb575iQ@mail.gmail.com
Whole thread Raw
In response to Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds  (Michael Lewis <mlewis@entrata.com>)
List pgsql-general
I see an issue with the operator. GIN index is capable of performing index scan and index-only scan.


Regards,
Ninad Shah

On Thu, 2 Sept 2021 at 20:57, Michael Lewis <mlewis@entrata.com> wrote:
This is showing many false positives from the index scan that get removed when the actual values are examined. With such a long search parameter, that does not seem surprising. I would expect a search on "raj nagar ghaziabad 201017" or something like that to yield far fewer results from the index scan. I don't know GIN indexes super well, but I would guess that including words that are very common will yield false positives that get filtered out later.

pgsql-general by date:

Previous
From: Ninad Shah
Date:
Subject: Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds
Next
From: Tom Lane
Date:
Subject: Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds