From: Stephan Vollmer <svollmer@gmx.de>
To: pgsql-general@postgresql.org
Subject: Re: Creation of tsearch2 index is very slow
Date: Sat, 21 Jan 2006 19:37:06 +0100
Message-ID: <43D27F52.8090003@gmx.de> (raw)
In-Reply-To: <6376.1137799359@sss.pgh.pa.us>
References: <43D0ED57.1020608@gmx.de>
<17454.1137771321@sss.pgh.pa.us>
<43D114B1.5030802@gmx.de>
<6376.1137799359@sss.pgh.pa.us>
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
Attachments:
signature.asc (application/pgp-signature, 249B) 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: svollmer@gmx.de, pgsql-general@postgresql.org
Subject: Re: Creation of tsearch2 index is very slow
In-Reply-To: <43D27F52.8090003@gmx.de>
* 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