From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Skip Evans <skip(at)bigskypenguin(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL full text vs. MySQL |
Date: | 2008-05-27 09:06:15 |
Message-ID: | 483BCF07.9060701@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Skip Evans wrote:
> I am wondering if I could get some opinions on PostgreSQL's full text
> versus MySQL's and specifically I have not been able to find
> documentation that MySQL supports lexeme type full text, able to locate
> root words the way PostgreSQL 8.3 does.
MySQL's full-text search is:
1. Isam-based only (afaik), so no transactions for you.
2. Much simpler than PostgreSQL's full-text searching
Whether #2 is good/bad depends if you want simple or flexible. If you're
starting to think about stemming or custom requirements already, I think
you're probably ruling out MySQL anyway. From my (admittedly limited)
knowledge of MySQL fti, you're able to replace the standard list of
stopwords and set a minimum number of letters to count as a word and
that's about it.
The PostgreSQL system lets you chain dictionaries together, have
multiple dictionaries per configuration or write a custom parser if
really required. Complicated, but flexible.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2008-05-27 09:30:51 | Re: [GENERAL] Fragments in tsearch2 headline |
Previous Message | aasat | 2008-05-27 08:48:12 | array of composite types to refcusor |