From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: string_to_array eats too much memory? |
Date: | 2006-11-08 10:03:40 |
Message-ID: | 4551AB7C.2040009@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I'm testing how GIN scales.
Have a look at http://www.sigaev.ru/cvsweb/cvsweb.cgi/ftsbench/ - utility is
specially developed for measuring performance of full-text solutions ( now it
supports PgSQL( GiST, GIN ) and MySQL ). Right now I'm searching good query
statistic for simulate load, but this data is a closed information in
internet-wide search engines :(
> ? I thought GIN is superior than tsearch2.
>
> From your GIN proposal posted to pgsql-hackers:
>
> "The primary goal of the Gin index is a scalable full text search in
> PostgreSQL"
GIN itself is a just a tool for speedup searches, linguistic part is still in
tsearch2.
It's possible to use tsearch2 without any indexes at all. GiST and GIN is a way
to speedup searches.
Of course, you can develop another framework for full text search and framework
may use GIN as it wish :)
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-11-08 10:19:54 | Re: [HACKERS] Bug in WAL backup documentation |
Previous Message | Magnus Hagander | 2006-11-08 09:47:29 | Re: string_to_array eats too much memory? |