Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxx> 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



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not
      match

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux