Re: Full Text Index Scanning
| От | Matt Warner |
|---|---|
| Тема | Re: Full Text Index Scanning |
| Дата | |
| Msg-id | AANLkTi=aFz58MtGBt5eYav-U2SEexnqf26iQ-D7KFYD4@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Full Text Index Scanning (Matt Warner <matt@warnertechnology.com>) |
| Ответы |
Re: Full Text Index Scanning
|
| Список | pgsql-general |
If I understand this, it looks like this approach allows me to match the beginnings and endings of words, but not the middle sections. Is that correct? That is, if I search for "jag" I will find "jaeger" but not "lobenjager".
Or am I (again) not understanding how this works?
TIA,
Matt
On Sun, Jan 30, 2011 at 9:59 AM, Matt Warner <matt@warnertechnology.com> wrote:
Aha! Thanks for pointing that out. It's indexing now.Thanks!MattOn Sun, Jan 30, 2011 at 9:12 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:Matt Warner <matt@warnertechnology.com> writes:That's not the same case he tested. The single-parameter form of
> Doesn't seem to work either. Maybe something changed in 9.1?
> create index test_idx on testtable using gin(to_tsvector(wordcolumn||'
> '||reverse(wordcolumn)));
> ERROR: functions in index expression must be marked IMMUTABLE
to_tsvector isn't immutable, because it depends on the default text
search configuration parameter. It should work, AFAICS, with the
two-parameter form.
regards, tom lane
В списке pgsql-general по дате отправления: