Re: Querying a table with jaccard similarity with 1.6 million records take 12 seconds

From: Michael Lewis <mlewis(at)entrata(dot)com>
To: Ninad Shah <nshah(dot)postgres(at)gmail(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 15:27:28
Message-ID: CAHOFxGruzhrb0SeD=5jLjgB+P-h3WpkbMyGfaje4Uuf_EVu5wQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vano Beridze 2021-09-02 17:38:38 Upgrade 9.5 cluster on Ubuntu 16.04
Previous Message M Tarkeshwar Rao 2021-09-02 15:11:25 RE: memory consumption of memory for postgres db container