From: Oleg Bartunov <oleg@sai.msu.su>
To: Martijn van Oosterhout <kleptog@svana.org>
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 16:29:13 +0300 (MSK)
Message-ID: <Pine.GSO.4.63.0601211619541.14417@ra.sai.msu.su> (raw)
In-Reply-To: <20060121130830.GA9955@svana.org>
References: <17454.1137771321@sss.pgh.pa.us>
<20060120170452.GC31908@svana.org>
<26153.1137784469@sss.pgh.pa.us>
<20060120201036.GE31908@svana.org>
<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>
On Sat, 21 Jan 2006, Martijn van Oosterhout wrote:
> However, IMHO, this algorithm is optimising the wrong thing. It
> shouldn't be trying to split into sets that are far apart, it should be
> trying to split into sets that minimize the number of set bits (ie
> distance from zero), since that's what's will speed up searching.
Martijn, you're right! We want not only to split page to very
different parts, but not to increase the number of sets bits in
resulted signatures, which are union (OR'ed) of all signatures
in part. We need not only fast index creation (thanks, Tom !),
but a better index. Some information is available here
http://www.sai.msu.su/~megera/oddmuse/index.cgi/Tsearch_V2_internals
There are should be more detailed document, but I don't remember where:)
> That's harder though (this algorithm does approximate it sort of)
> and I havn't come up with an algorithm yet
Don't ask how hard we thought :)
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, Research Scientist, Head of AstroNet (www.astronet.ru),
Sternberg Astronomical Institute, Moscow University, Russia
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(495)939-16-83, +007(495)939-23-83
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: oleg@sai.msu.su, kleptog@svana.org, tgl@sss.pgh.pa.us, rjpeace@earthlink.net
Subject: Re: [GENERAL] Creation of tsearch2 index is very slow
In-Reply-To: <Pine.GSO.4.63.0601211619541.14417@ra.sai.msu.su>
References: <17454.1137771321@sss.pgh.pa.us> <20060120170452.GC31908@svana.org> <26153.1137784469@sss.pgh.pa.us> <20060120201036.GE31908@svana.org> <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>
* 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