Re: OK, does anyone have any better ideas?

mlw <markw(at)mohawksoft(dot)com> writes:
> I have a working version of a text search engine. I want to make it work
> for Postgres (I will be releasing it GPL). It can literally find the
> occurrence of a string of words within 5 million records in a few
> milliseconds.

Where are the records coming from? Are they inside the database?
(If not, why do you care about integrating this with Postgres?)

It seems like the right way to integrate this sort of functionality
is to turn it into a kind of index, so that you can do

SELECT * FROM mytable WHERE keyfield ~~~ 'search string';

where ~~~ is the name of some operator that is associated with the
index. The temporary-table approach you are taking seems inherently
klugy, and would still be awkward even if we had functions returning
recordsets...

regards, tom lane