From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Stephan Vollmer <svollmer@gmx.de>
Cc: pgsql-general@postgresql.org
Subject: Re: Creation of tsearch2 index is very slow
Date: Fri, 20 Jan 2006 12:14:35 -0500
Message-ID: <25127.1137777275@sss.pgh.pa.us> (raw)
In-Reply-To: <20060120170452.GC31908@svana.org>
References: <43D0ED57.1020608@gmx.de>
<17454.1137771321@sss.pgh.pa.us>
<20060120170452.GC31908@svana.org>
Martijn van Oosterhout <kleptog@svana.org> writes:
> The cost on inserting would generally go to either penalty, or
> picksplit. Certainly if you're inserting lots of values in a short
> interval, I can imagine picksplit being nasty, since the algorithms for
> a lot of datatypes are not really reknown for their speed.
Tut tut ... in the words of the sage, it is a capital mistake to
theorize in advance of the data. You may well be right, but on the
other hand it could easily be something dumb like an O(N^2) loop over
a list structure.
I'll post some gprof numbers after Stephan sends me the dump. We
should probably move the thread to someplace like pgsql-perform, too.
regards, tom lane
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: tgl@sss.pgh.pa.us, kleptog@svana.org, svollmer@gmx.de, pgsql-general@postgresql.org
Subject: Re: Creation of tsearch2 index is very slow
In-Reply-To: <25127.1137777275@sss.pgh.pa.us>
* 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