From: Maarten Boekhold <boekhold@tibco.com>
To: Alexander Schneider <alex@alexander-schneider.de>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Full-Text-Indexing
Date: Tue, 15 Jun 1999 13:52:32 +0200
Message-ID: <37663E80.4EBEC2B1@tibco.com> (raw)
References: <1282947191-50950897@mail.isolution.de>
> 1) Why should I use "varchar(n)" instead of "text" though the space for a
> varchar-field is larger than text (varchar: 4byte+n, text: 2byte+n)? Is
> it more efficient for queries?
No reason, I think it the code would even work without changes if you
use 'text' fields...
> 2) I would like a table where I can insert/update/delete the stop-words
> instead of an array inside the code. This would also help in lower the
> words to search for in the query. Are there any grave performance
> penaltys for this solution? It is much more flexible and I would trade a
> small performance loss for this flexibility. [I cannot program in C so
> maybe there is a volunteer who could write this little snippet for me?
The problem here is that without resorting to some advanced stuff using
shared memory or whatever that table would have to be read by every backend
starting up, which might be some significant overhead.
I'm still hoping somebody can rewrite this stuff to use some specific indexing
method so we don't have to go the way of introducing this intermediate table
(i.e. store the substring/oid pairs directly in a btree item and use some
new index access method to take something like field ~= 'rolling NOT stone'
to search this index).
Maarten
--
Maarten Boekhold, boekhold@tibco.com
TIBCO Finance Technology Inc.
The Atrium
Strawinskylaan 3051
1077 ZX Amsterdam, The Netherlands
tel: +31 20 3012158, fax: +31 20 3012358
http://www.tibco.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: boekhold@tibco.com, alex@alexander-schneider.de
Subject: Re: [SQL] Full-Text-Indexing
In-Reply-To: <37663E80.4EBEC2B1@tibco.com>
References: <1282947191-50950897@mail.isolution.de> <37663E80.4EBEC2B1@tibco.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox