Re: indexing large "text" attributes ... ERROR: maximum size is 8191 - Mailing list pgsql-general

From Tom Lane
Subject Re: indexing large "text" attributes ... ERROR: maximum size is 8191
Date
Msg-id 9164.1186367826@sss.pgh.pa.us
Whole thread Raw
In response to Re: indexing large "text" attributes ... ERROR: maximum size is 8191  (Benjamin Arai <me@benjaminarai.com>)
List pgsql-general
Benjamin Arai <me@benjaminarai.com> writes:
> 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)

Right.

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

Wrong.  A btree index on strMessage is utterly worthless for checking
that pattern match, and even if it did work, there's no point in using
a second index to check it rather than fetching the heap entry.

            regards, tom lane

pgsql-general by date:

Previous
From: Benjamin Arai
Date:
Subject: Re: indexing large "text" attributes ... ERROR: maximum size is 8191
Next
From: hanasaki
Date:
Subject: Re: HA, failover and load balancing / howto?