| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug of pg_trgm? |
| Date: | 2012-09-06 21:09:48 |
| Message-ID: | 3441.1346965788@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 08/20/2012 01:26 PM, Tom Lane wrote:
>> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
>>> OK. Attached patch fixes the problem as you suggested, i.e., it backs up
>>> "endword" if the second loop exits in an escape pair.
>> Applied with a bit of further adjustment of the comments. Thanks!
> When moving to a release with this change, will users need to reindex
> trgm indexes?
No. This only changes extraction of search trigrams from a LIKE pattern,
not extraction of trigrams from text to be indexed.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-09-06 21:13:26 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |
| Previous Message | Robert Haas | 2012-09-06 21:08:11 | Re: BUG #7521: Cannot disable WAL log while using pg_dump |