| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Amit Langote <amitlangote09(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Behavior of a pg_trgm index for 2 (or < 3) character LIKE queries |
| Date: | 2013-05-30 19:25:00 |
| Message-ID: | CAPpHfdtGkbXjrPkxziRdc9dNnurGAYgivYLNV0_LoBQ329fS7A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 30, 2013 at 12:49 PM, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>wrote:
> following emails are discussed about partial match of pg_trgm. I hope
> will this help.
> <
> http://www.postgresql.org/message-id/CAHGQGwFJshvV2nGME19wdTW9teFw_w7h2ns4E+YYsjkB9WdWDQ@mail.gmail.com
> >
> as you may know, if search string contains multibyte characters
> trigram key is converted to CRC of 4 byte and it is used as key.
> (but only use upper 3 byte from CRC)
> so we can do partial matching if KEEPONLYALNUM is enabled.
>
Please, read the further discussion on that thread. We can't do partial
matching because of CRC independently of KEEPONLYALNUM.
------
With best regards,
Alexander Korotkov.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-05-30 20:07:09 | Re: Vacuum, Freeze and Analyze: the big picture |
| Previous Message | Andres Freund | 2013-05-30 19:22:38 | Re: Freezing without write I/O |