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

From Michael Lewis
Subject Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds
Date
Msg-id CAHOFxGruzhrb0SeD=5jLjgB+P-h3WpkbMyGfaje4Uuf_EVu5wQ@mail.gmail.com
Whole thread Raw
In response to Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds  (Ninad Shah <nshah.postgres@gmail.com>)
Responses Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds  (Ninad Shah <nshah.postgres@gmail.com>)
Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
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: M Tarkeshwar Rao
Date:
Subject: RE: memory consumption of memory for postgres db container
Next
From: Vano Beridze
Date:
Subject: Upgrade 9.5 cluster on Ubuntu 16.04