X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E33769DC85C for ; Sat, 21 Jan 2006 14:37:23 -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 21211-01 for ; Sat, 21 Jan 2006 14:37:21 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by postgresql.org (Postfix) with SMTP id 164779DC801 for ; Sat, 21 Jan 2006 14:37:17 -0400 (AST) Received: (qmail invoked by alias); 21 Jan 2006 18:37:15 -0000 Received: from p54A662C7.dip.t-dialin.net (EHLO athlon64) [84.166.98.199] by mail.gmx.net (mp006) with SMTP; 21 Jan 2006 19:37:15 +0100 X-Authenticated: #594052 Received: from localhost (HELO [127.0.0.1]) [127.0.0.1] by athlon64 (192.168.0.2) (userid 3) with ESMTP (Classic Hamster Version 2.1 Build 2.1.0.0) ; Sat, 21 Jan 2006 19:37:09 +0100 Message-ID: <43D27F52.8090003@gmx.de> Date: Sat, 21 Jan 2006 19:37:06 +0100 From: Stephan Vollmer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051201 Thunderbird/1.5 Mnenhy/0.7.3.0 MIME-Version: 1.0 To: pgsql-general@postgresql.org Subject: Re: Creation of tsearch2 index is very slow References: <43D0ED57.1020608@gmx.de> <17454.1137771321@sss.pgh.pa.us> <43D114B1.5030802@gmx.de> <6376.1137799359@sss.pgh.pa.us> In-Reply-To: <6376.1137799359@sss.pgh.pa.us> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=8D46FCF8 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4F286EDFAF0429FEA7647227" X-Posting-Agent: Hamster/2.1.0.0 X-Y-GMX-Trusted: 0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.082 required=5 tests=[AWL=0.082] X-Spam-Score: 0.082 X-Spam-Level: X-Archive-Number: 200601/1057 X-Sequence-Number: 90002 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4F286EDFAF0429FEA7647227 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Tom Lane wrote: > The problem seems to be mostly tsearch2's fault rather than the general= > GIST code. I've applied a partial fix to 8.1 and HEAD branches, which > you can find here if you're in a hurry for it: > http://archives.postgresql.org/pgsql-committers/2006-01/msg00283.php > (the gistidx.c change is all you need for tsearch2) Thanks for all your time and work you and the other guys are spending on this matter! I'll look into the new version, but a.p.o seems to be unreachable at the moment. > There is some followup discussion in the pgsql-performance list. It > seems possible that we can get another factor of 10 or better with a > smarter picksplit algorithm --- but that patch will probably be too > large to be considered for back-patching into the stable branches. I've already been following the discussion on pgsql-perform, although I have to admit that don't understand every detail of the tsearch2 implementation. :-) Thus, I'm sorry that I won't be able to help directly on that problem. But it is interesting to read anyway. Best regards, - Stephan --------------enig4F286EDFAF0429FEA7647227 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD0n9VjY05go1G/PgRArBqAJ4ydI97FAgXQUjx8nxduAPH74aaIQCeMjLU sey3aS73bsV/s6HGZviCFuM= =iPyV -----END PGP SIGNATURE----- --------------enig4F286EDFAF0429FEA7647227--