Greetings,
I am trying to test out the performance of the contrib/fulltextindex
package and I am getting horrid performance results.
The Setup:
I created a simple table, ST (id SERIAL, body varchar(1024), which is to be
searched. I created the ST_FTI table, trigger and indices as per
slow; what am I doing wrong?
Date: Wed, 22 Aug 2001 11:28:04 -0400
You've vacuum analyze 'd the database, haven't you?
-Mitch
There is exactly one sentence (row) that has the strings 'Newton' and
'Kepler' in it. That is my target. For a straight select on ST:
select * from st where body
Paul C. [EMAIL PROTECTED] writes:
Indeed, the cost to look up a single string in the st_fti
table is way high:
select * from st_fti where string ~ '^kepler';
costs 36703.40, AND its doing a Seq Scan on st_fti, even though an index
exists.
Have you done a VACUUM ANALYZE on st_fti? Are
Did you vacuum after
populating the tables?
If not you should do it
On Wed, Aug 22, 2001 at 11:08:55AM -0400, Paul C. wrote:
Greetings,
I am trying to test out the performance of the contrib/fulltextindex
package and I am getting horrid performance results.
The Setup:
I created a
