From: Martijn van Oosterhout <kleptog@svana.org>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ron <rjpeace@earthlink.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: [GENERAL] Creation of tsearch2 index is very slow
Date: Sat, 21 Jan 2006 21:35:58 +0100
Message-ID: <20060121203558.GC9955@svana.org> (raw)
In-Reply-To: <Pine.GSO.4.63.0601211808490.14417@ra.sai.msu.su>
References: <26583.1137788505@sss.pgh.pa.us>
<20060120205132.GF31908@svana.org>
<26958.1137791955@sss.pgh.pa.us>
<20060120213754.GG31908@svana.org>
<7.0.1.0.2.20060120174141.039b03e8@earthlink.net>
<6111.1137797436@sss.pgh.pa.us>
<20060121130830.GA9955@svana.org>
<Pine.GSO.4.63.0601211619541.14417@ra.sai.msu.su>
<20060121150424.GB9955@svana.org>
<Pine.GSO.4.63.0601211808490.14417@ra.sai.msu.su>
On Sat, Jan 21, 2006 at 06:22:52PM +0300, Oleg Bartunov wrote:
> >I see how it works, what I don't quite get is whether the "inverted
> >index" you refer to is what we're working with here, or just what's in
> >tsearchd?
>
> just tsearchd. We plan to implement inverted index into PostgreSQL core
> and then adapt tsearch2 to use it as option for read-only archives.
Hmm, had a look and think about it and I think I see what you mean by
an inverted index. I also think your going to have a real exercise
implementing it in Postgres because postgres indexes work on the basis
of one tuple, one index entry, which I think your inverted index
doesn't do.
That said, I think GiST could be extended to support your case without
too much difficulty. Interesting project though :)
BTW, given you appear to have a tsearch2 index with some real-world
data, would you be willing to try some alternate picksplit algorithms
to see if your gevel module shows any difference?
Have a nice day,
--
Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
Attachments:
signature.asc (application/pgp-signature, 188B) download
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: kleptog@svana.org, oleg@sai.msu.su, tgl@sss.pgh.pa.us, rjpeace@earthlink.net
Subject: Re: [GENERAL] Creation of tsearch2 index is very slow
In-Reply-To: <20060121203558.GC9955@svana.org>
* 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