Re: Full Text Index Scanning

From: Matt Warner <matt(at)warnertechnology(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, pgsql-general(at)postgresql(dot)org
Subject: Re: Full Text Index Scanning
Date: 2011-01-30 18:13:26
Message-ID: AANLkTi=aFz58MtGBt5eYav-U2SEexnqf26iQ-D7KFYD4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)warnertechnology(dot)com>wrote:

> Aha! Thanks for pointing that out. It's indexing now.
>
> Thanks!
>
> Matt
>
>
> On Sun, Jan 30, 2011 at 9:12 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Matt Warner <matt(at)warnertechnology(dot)com> writes:
>> > 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
>>
>> That's not the same case he tested. The single-parameter form of
>> 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
>>
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-01-30 18:36:38 Re: Full Text Index Scanning
Previous Message Matt Warner 2011-01-30 17:59:16 Re: Full Text Index Scanning