| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Teju Jakkidi vlogs <teja(dot)jakkidi05(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Query taking long with levenshtein function |
| Date: | 2023-02-28 23:30:51 |
| Message-ID: | 1278258.1677627051@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Teju Jakkidi vlogs <teja(dot)jakkidi05(at)gmail(dot)com> writes:
> We have a query as below which uses the levenshtein function to compare
> strings.
> SELECT "name", levenshtein("name",'some string') as p FROM table1
> where levenshtein("name",'some string') <= 2 order by p desc;
> We have a GIST index built on top of this table as below:
> CREATE INDEX gist_idx ON table1 USING GIST("name");
AFAIK, that index is completely useless for this query. I don't
really see a good way to index it either --- "levenshtein distance
less than X" seems like a not very tractable requirement. Can
you formulate your matching rules some other way?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edward J. Sabol | 2023-03-01 00:22:08 | Re: Query taking long with levenshtein function |
| Previous Message | Teju Jakkidi vlogs | 2023-02-28 23:11:55 | Query taking long with levenshtein function |