Re: tsearch comments

From: Björn Metzdorf <bm(at)turtle-entertainment(dot)de>
To: "Teodor Sigaev" <teodor(at)stack(dot)net>
Cc: "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: tsearch comments
Date: 2003-01-23 11:49:41
Message-ID: 018a01c2c2d5$83dfa590$81c206d4@office.turtleentertainment.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> > Yes, I don't see that problem either. The locale and the configuration
of
> > dictionaries do not change while running the postmaster, do they?
> I forgot parser too.
>
> Parser and dictionaries will be changed after gmake install
(contrib/tsearch)
> :), without restarting postmaster.
>
> In common case, we can't set iscachable option to txt2txtidx, but if you
know
> what you do you can set it. May be
> some comments must be included in README.

Ok, but then it should be sufficient to recreate the txt2txtidx function
and/or the index after a change of parser and dictionaries. So generally
spoken, the index function approach to tsearch works, if you take care of
that. I gladly recreate the function and/or index from time to time, if I
can do without that additional column, bloated dump and slow trigger.

This is very good news, as this is a very easy approach to having an easy to
use fulltextsearch in postgresql.

> > Great news! Any comments on the new version? Snowball support?
txt2txtidx
> > without morphology?
> Snowball, ISpell....
> SQL-level for configure parsers and dictionaries.
> SQL-level for configure map (which dictionary for each type of lexem).
> Just wait :)

Wow, sounds great!

Regards,
Bjoern

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alan T. Miller 2003-01-23 12:26:31 I was spoiled by the MySQL timestamp field
Previous Message Teodor Sigaev 2003-01-23 11:36:48 Re: tsearch comments