From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
Cc: | Michael Riess <mlriess(at)gmx(dot)de>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: TSearch2 vs. Apache Lucene |
Date: | 2005-12-06 17:27:31 |
Message-ID: | 200512061727.jB6HRVN18473@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Oleg Bartunov wrote:
> Folks,
>
> tsearch2 and Lucene are very different search engines, so it'd be unfair
> comparison. If you need full access to metadata and instant indexing
> you, probably, find tsearch2 is more suitable then Lucene. But, if
> you could live without that features and need to search read only
> archives you need Lucene.
>
> Tsearch2 integration into pgsql would be cool, but, I see no problem to
> use tsearch2 as an official extension module. After completing our
> todo, which we hope will likely happens for 8.2 release, you could
> forget about Lucene and other engines :) We'll be available for developing
> in spring and we estimate about three months for our todo, so, it's
> really doable.
Agreed. There isn't anything magical about a plug-in vs something
integrated, as least in PostgreSQL. In other database, plug-ins can't
fully function as integrated, but in PostgreSQL, everything is really a
plug-in because it is all abstracted.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Ameet Kini | 2005-12-06 17:44:03 | postgresql performance tuning |
Previous Message | Oleg Bartunov | 2005-12-06 17:14:14 | Re: TSearch2 vs. Apache Lucene |