pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Oleg Bartunov <oleg@sai.msu.su>
To: Steve Atkins <steve@blighty.com>
Cc: pgsql-general@postgresql.org
Subject: Re: Text Search vs MYSQL vs Lucene
Date: Thu, 9 Sep 2004 21:56:59 +0400 (MSD)
Message-ID: <Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su> (raw)
In-Reply-To: <20040909142006.GA24396@gp.word-to-the-wise.com>
References: <414052F4.5050000@portalvu.com>
	<20040909142006.GA24396@gp.word-to-the-wise.com>

I'd say indexing of 2 TB of data would be a very costly even for
standalone solution ( no relational database ).
Ideal solution would be to have tsearch2 for current documents and
standalone solution for archive documents. If these solutions share
common parsers,dictionaries and ranking schemes it would be easy to
combine results from two queries. We have prototype for standalone
solution - it's based on OpenFTS, which is already tsearch2 compatible.


	Oleg
On Thu, 9 Sep 2004, Steve Atkins wrote:

> On Thu, Sep 09, 2004 at 07:56:20AM -0500, Vic Cekvenich wrote:
>
> > What would be performance of pgSQL text search vs MySQL vs Lucene (flat
> > file) for a 2 terabyte db?
> > thanks for any comments.
>
> My experience with tsearch2 has been that indexing even moderately
> large chunks of data is too slow to be feasible. Moderately large
> meaning tens of megabytes.
>
> Your milage might well vary, but I wouldn't rely on postgresql full
> text search of that much data being functional, let alone fast enough
> to be useful. Test before making any decisions.
>
> If it's a static or moderately static text corpus you're probably
> better using a traditional FTS system anyway (tsearch2 has two
> advantages - tight integration with pgsql and good support for
> incremental indexing).
>
> Two terabytes is a lot of data. I'd suggest you do some research on
> FTS algorithms rather than just picking one of the off-the-shelf FTS
> systems without understanding what they actually do. "Managing
> Gigabytes" ISBN 1-55860-570-3 covers some approaches.
>
> Cheers,
>   Steve
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html
>

	Regards,
		Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83



view thread (6+ messages)

Message-ID: <Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su>
Permalink:  ../Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su/
Also on:    postgresql.org/message-id/Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: oleg@sai.msu.su, steve@blighty.com, pgsql-general@postgresql.org
  Subject: Re: Text Search vs MYSQL vs Lucene
  In-Reply-To: <Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su>
  References: <414052F4.5050000@portalvu.com> <20040909142006.GA24396@gp.word-to-the-wise.com> <Pine.GSO.4.58.0409092151250.12822@ra.sai.msu.su>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox