Re: indexing large "text" attributes ... ERROR: maximum size is 8191

Поиск
Список
Период
Сортировка
От Benjamin Arai
Тема Re: indexing large "text" attributes ... ERROR: maximum size is 8191
Дата
Msg-id 2CA48A10-112A-4838-B572-BBD96278C974@benjaminarai.com
обсуждение исходный текст
Ответ на Re: indexing large "text" attributes ... ERROR: maximum size is 8191  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: indexing large "text" attributes ... ERROR: maximum size is 8191
Список pgsql-general
To clarify, I am using the GIN index to perform the tsearch2 queries
which works fine.  The problem with this is that you cannot use the
tsearch2 fields since they are vectors to do exact match searches.
The tsearch2 webpage says to do something like

         SELECT intindex, strTopic FROM tblmessages
                 WHERE idxfti @@ to_tsquery('default', 'gettysburg &
address')
                 AND strMessage ~* '.*men are created equal.*';
          intindex |           strtopic
         ----------+------------------------------
                 6 | Gettysburg address quotation
         (1 row)

Which would mean I would have to create index on strMessage.  Right?

Benjamin

On Aug 5, 2007, at 7:17 PM, Tom Lane wrote:

> Benjamin Arai <me@benjaminarai.com> writes:
>> I am actually creating a GIN index on another field but I need to
>> index the original "text" field to perform exact phrase matches.
>
> Why do you think an extra index will be useful for that?  Especially
> a btree index?
>
>             regards, tom lane
>


В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: indexing large "text" attributes ... ERROR: maximum size is 8191
Следующее
От: Tom Lane
Дата:
Сообщение: Re: indexing large "text" attributes ... ERROR: maximum size is 8191