From: | Chris <dmagick(at)gmail(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, aBBISh <abbish(at)163(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to use the full text index feature on PostgreSQL |
Date: | 2006-08-14 00:23:05 |
Message-ID: | 44DFC269.4030207@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alvaro Herrera wrote:
> Joshua D. Drake wrote:
>> Matthew T. O'Connor wrote:
>>> Chris wrote:
>>>> aBBISh wrote:
>>>> You need to install & setup tsearch2.
>>>>
>>>> I have a small article about how to do that here:
>>>>
>>>> http://www.designmagick.com/article/27/
>>> Also on page 3 you say, "(normal indexes will only index the first 255
>>> characters of a 'text' field)."
>>>
>>> Is that true?
>> I thought it was the first 8k? There is also an article here:
>>
>> http://www.devx.com/opensource/Article/21674/1954?pf=true
>
> Neither is true. If you create an index on a text column, and that
> column contains a row above the size limit, an error will result.
> There's no mechanism in place to truncate what's indexed in order to
> make it fit the maximum index tuple size; you can do it yourself using
> an expressional index if you want, of course.
>
> The maximum is a bit above 2kB (assuming 8kB pages), but keep in mind
> that some stuff is compressed before being indexed, so the actual data
> length may be higher.
>
Thanks for the tips. I've fixed them up in the article :)
--
Postgresql & php tutorials
http://www.designmagick.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Chris | 2006-08-14 06:01:28 | Re: Best approach for a "gap-less" sequence |
Previous Message | Richard Broersma Jr | 2006-08-13 23:36:38 | Re: Connection string |