From: | Benjamin Arai <me(at)benjaminarai(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: indexing large "text" attributes ... ERROR: maximum size is 8191 |
Date: | 2007-08-06 02:23:12 |
Message-ID: | 2CA48A10-112A-4838-B572-BBD96278C974@benjaminarai.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)benjaminarai(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-06 02:37:06 | Re: indexing large "text" attributes ... ERROR: maximum size is 8191 |
Previous Message | Tom Lane | 2007-08-06 02:17:18 | Re: indexing large "text" attributes ... ERROR: maximum size is 8191 |