Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Slow running to_tsvector (tsearch2 in PG 8.2.3)


  • From: Henrik Zagerholm <henke(at)mac(dot)se>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Markus Schiltknecht <markus(at)bluegap(dot)ch>, pgsql-general(at)postgresql(dot)org
  • Subject: Re: Slow running to_tsvector (tsearch2 in PG 8.2.3)
  • Date: Wed, 21 Feb 2007 16:03:04 +0100
  • Message-id: <A6488B00-7975-49DD-B6D5-EA6B34C27449(at)mac(dot)se>


21 feb 2007 kl. 15:44 skrev Tom Lane:

Markus Schiltknecht <markus(at)bluegap(dot)ch> writes:
Henrik Zagerholm wrote:
Is this normal? What can I tweak in postgresql.conf to speed up big
to_tsvector()?

Hm.. seems not too unreasonable to me.
Take a look at the stemmers or dictionaries involved. What do you use there?
I tried both the default english and simple stemmers. Simple was a little bit faster but not much.

What is your configuration ? to_tsvector does a lot of work.
I haven't tweaked the postgresql.conf yet. What should I focus on? work_mem, shared_buffers?

Also, I wonder how much of the time went into to_tsvector() and how much
into updating the GIST or GIN index that I suppose is on the column.
For a full update like this it might make sense to drop the index,
update the column, rebuild the index from scratch.
I actually tested to remove the GIN index on the vectors column and it didn't have any noticeable effect. Maybe because its the only tuple in the database.

Thanks for all your input!

regards, henrik


			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings




Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group