On Wed, 21 Feb 2007, Henrik Zagerholm wrote:
Hello list,
I've been testing tsearch2 for a while and I recently noticed some really
slow queries.
This is a quite big document so the times are maybe accurate.
The document has about 194 000 words.
I put all the data in tbl_fulltext.fulltext_text and then did a
update tbl_fulltext set vectors = to_tsvector(fulltext_text);
Which takes about 80 seconds to complete.
The hardware is a Pentium 4 2.8GHz with 1GB HyperX memory.
Is this normal? What can I tweak in postgresql.conf to speed up big
to_tsvector()?
What is your configuration ? to_tsvector does a lot of work.
Regards,
Henrik
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
