| From: | Ninad Shah <nshah(dot)postgres(at)gmail(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | balasubramanian c r <crbs(dot)siebel(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds |
| Date: | 2021-09-02 19:43:05 |
| Message-ID: | CAOFEiBd1Vi_bZTLh81RTCBPODnfr_7R8Dv-fzLhCcSZAb575iQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)entrata(dot)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.
>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-02 19:44:09 | Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds |
| Previous Message | Ninad Shah | 2021-09-02 19:42:16 | Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds |