| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Jan Urbański <j(dot)urbanski(at)students(dot)mimuw(dot)edu(dot)pl> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: gsoc, oprrest function for text search take 2 |
| Date: | 2008-08-14 21:33:04 |
| Message-ID: | 20080814213304.GI4232@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jan Urbański wrote:
> Heikki Linnakangas wrote:
>> Sounds like a plan. In (2), it's even better to detoast the values
>> lazily. For a typical one-word tsquery, the binary search will only
>> look at a small portion of the elements.
>
> Hm, how can I do that? Toast is still a bit black magic to me... Do you
> mean I should stick to having Datums in TextFreq?
Store both the Datum and the text *. If the latter is NULL, then grab
the datum, detoast and store the result in the text *. Next time you
need to look at it, it's already detoasted.
I don't know the code so I have no idea if this is applicable.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2008-08-14 21:42:38 | Re: gsoc, oprrest function for text search take 2 |
| Previous Message | Hannu Krosing | 2008-08-14 21:05:56 | Re: proposal sql: labeled function params |