| From: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Giuseppe Broccolo <giuseppe(dot)broccolo(at)2ndquadrant(dot)it>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Question about trigram GIST index |
| Date: | 2014-12-18 19:33:39 |
| Message-ID: | CAAXGW-xDkCfK3v1vVWzbA2D4nGYj46DCxuNtEiqQkuej8oggNg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jeff, I'm not seeing that limitation.
On Thu, Dec 18, 2014 at 10:33 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
> On Thu, Dec 18, 2014 at 10:00 AM, Giuseppe Broccolo <
> giuseppe(dot)broccolo(at)2ndquadrant(dot)it> wrote:
>>
>> I'm not sure about the '%' operator, but I'm sure that the GIST index
>> will never be used in the
>>
>> SELECT * FROM users WHERE lower(name) LIKE '%john%';
>>
>> query; it is used for left or right anchored search, such as 'john%' or
>> '%john'.
>>
>
> The point of the gist_trgm_ops operator is specifically to overcome that
> limitation.
>
> It is pretty awesome.
>
> Cheers,
>
> Jeff
>>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2014-12-18 20:03:13 | Re: Question about trigram GIST index |
| Previous Message | Jeff Janes | 2014-12-18 18:33:33 | Re: Question about trigram GIST index |