Re: tsearch V2 (Was: Re: Two weeks to feature freeze)

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: The Hermit Hacker <scrappy(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: tsearch V2 (Was: Re: Two weeks to feature freeze)
Date: 2003-06-20 07:04:13
Message-ID: 1056092652.1759.11.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker kirjutas R, 20.06.2003 kell 08:28:
> On Fri, 20 Jun 2003, Tom Lane wrote:
>
> > > On Fri, 20 Jun 2003, The Hermit Hacker wrote:
> > > Is there a strong reason why tsearch isn't in gborg?
> >
> > I think text search is a pretty important facility that should
> > eventually be part of the core distribution. It's more likely to get
> > there from contrib than from gborg ...
>
> Why part of the core distribution, and not just left as a loadable module,
> like it is now?

I remember Tom saying that builtin functions calls are a lot faster than
loadable C functions.

If that can be fixed, then it *could* stay loadable.

Also, having built-in full text indexing is very desirable. And I don't
see any even nearly as good competing fulltext indexing modules
anywhere.

If we had to move something *out* of core in order to get tsearch in,
then I personally would not mind if all geometry types go to gborg, but
I'm sure there are some users who would mind ;)

---------------
Hannu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kallol Nandi 2003-06-20 07:12:07 JDBC in PostgreSql for Linux
Previous Message Ivar 2003-06-20 06:26:11 Re: Is there any way to make post to newsgroups faster ?