| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Question about trigram GIST index |
| Date: | 2014-12-18 17:18:52 |
| Message-ID: | 18097.1418923132@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> writes:
> So, for my use case I simply need to search for a case insensitive
> substring. It need not be super exact. It seems like there are two ways I
> can do this:
> CREATE INDEX idx_users_name ON users USING GIST(lower(name) gist_trgm_ops);
> SELECT * FROM users WHERE lower(name) LIKE '%john%';
> Or I can do it like this:
> CREATE INDEX idx_users_name ON users USING GIST(name gist_trgm_ops);
> SELECT * FROM users WHERE name % 'john';
Hm, I don't see anything in the pg_trgm docs suggesting that % is
case-insensitive. But in any case, I'd go with the former as being
more understandable to someone who knows standard SQL.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alessandro Ipe | 2014-12-18 17:31:42 | Re: Excessive memory used for INSERT |
| Previous Message | Robert DiFalco | 2014-12-18 17:12:16 | Question about trigram GIST index |