Janek Sendrowski <janek12@xxxxxx> wrote: > I already had a try with gist/gin-index-based trigramm search > (pg_trgm extension), fulltextsearch (tsearch2 extension) and a > pivot-based indexing (Fixed Query Array), but it's all to slow or > not suitable. When you tried tsearch2, did you use a trigger to store the tsvector, or did you use a functional index? I found the former to be a couple orders of magnitude faster with an index on court document text. Likewise, the trigram searches I used in production had wildly different performance depending on the similarity threshold or the LIMIT for KNN searches. You may want to get the most promising technology to run as fast as you can, and then post to the pgsql-performance list with the information suggested here: http://wiki.postgresql.org/wiki/SlowQueryQuestions The problems may be solvable, but nobody is likely to know what to suggest without more to work with. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
