X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 010199DC821
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat, 21 Jan 2006 16:36:35 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 47546-01
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat, 21 Jan 2006 16:36:34 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from svana.org (svana.org [125.62.94.225])
	by postgresql.org (Postfix) with ESMTP id 4DD469DC801
	for <pgsql-performance@postgresql.org>;
	Sat, 21 Jan 2006 16:36:31 -0400 (AST)
Received: from kleptog by svana.org with local (Exim 4.50)
	id 1F0PSo-0003RK-HT; Sun, 22 Jan 2006 07:35:58 +1100
Date: Sat, 21 Jan 2006 21:35:58 +0100
From: Martijn van Oosterhout <kleptog@svana.org>
To: Oleg Bartunov <oleg@sai.msu.su>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Ron <rjpeace@earthlink.net>,
	pgsql-performance@postgresql.org
Subject: Re: [GENERAL] Creation of tsearch2 index is very slow
Message-ID: <20060121203558.GC9955@svana.org>
Reply-To: Martijn van Oosterhout <kleptog@svana.org>
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>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1SQmhf2mF2YjsYvc"
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0601211808490.14417@ra.sai.msu.su>
X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6
X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522  48A7 6394 F08A 0DC6 7BE6
X-PGP-Key-URL: <http://svana.org/kleptog/0DC67BE6.pgp.asc>
User-Agent: Mutt/1.5.9i
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: kleptog@svana.org
X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.128 required=5 tests=[AWL=0.128]
X-Spam-Score: 0.128
X-Spam-Level: 
X-Archive-Number: 200601/397
X-Sequence-Number: 16875


--1SQmhf2mF2YjsYvc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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?
>=20
> 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,
--=20
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.

--1SQmhf2mF2YjsYvc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFD0psuIB7bNG8LQkwRAqsSAJ0dymQlux4JATsdWKjiUXO8uyvBywCfWUtX
LcGjTdBwHFMl3Vhvi9UHglE=
=mmZh
-----END PGP SIGNATURE-----

--1SQmhf2mF2YjsYvc--