DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327;
 d=earthlink.net;
	b=aqi4xk+ix+r20QJxwS/n62XmYF/XB1nHsKGI0utwM7myGRuGVSrP7+u/f3+v/+Kg;
	h=Received:Message-Id:X-Mailer:Date:To:From:Subject:In-Reply-To:References:Mime-Version:Content-Type:X-ELNK-Trace:X-Originating-IP;
Message-Id: <7.0.1.0.2.20060126202809.03838ab0@earthlink.net>
Date: Thu, 26 Jan 2006 20:55:46 -0500
To: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-performance@postgresql.org
From: Ron <rjpeace@earthlink.net>
Subject: Re: [GENERAL] Creation of tsearch2 index is very
In-Reply-To: <20060127010054.GD13501@surnet.cl>
References: <20060120213754.GG31908@svana.org>
	<7.0.1.0.2.20060120174141.039b03e8@earthlink.net>
	<6111.1137797436@sss.pgh.pa.us> <20060120225751.GA27230@uio.no>
	<6532.1137801157@sss.pgh.pa.us> <20060121000519.GA29755@uio.no>
	<6743.1137802990@sss.pgh.pa.us>
	<7.0.1.0.2.20060121064930.03aba810@earthlink.net>
	<18771.1137868073@sss.pgh.pa.us>
	<7.0.1.0.2.20060126190219.0388a918@earthlink.net>
	<20060127010054.GD13501@surnet.cl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 08:00 PM 1/26/2006, Alvaro Herrera wrote:
>Ron wrote:
> > At 01:27 PM 1/21/2006, Tom Lane wrote:
> > >Ron <rjpeace@earthlink.net> writes:
> > >> At 07:23 PM 1/20/2006, Tom Lane wrote:
> > >>> Well, we're trying to split an index page that's gotten full into
> > >>> two index pages, preferably with approximately equal numbers 
> of items in
> > >>> each new page (this isn't a hard requirement though).
>
> > After reading the various papers available on GiST and RD trees, I
> > think I have a decent suggestion.
>
>I for one don't understand what does your suggestion have to do with the
>problem at hand ... not that I have a better one myself.

We have two problems here.
The first is that the page splitting code for these indexes currently 
has O(N^2) performance.
The second is that whatever solution we do use for this 
functionality, we still need good performance during searches that 
use the index.  It's not clear that the solutions we've discussed to 
splitting index pages thus far will result in good performance during searches.

My suggestion is intended to address both issues.

If I'm right it helps obtain high performance during searches while 
allowing the index page splitting code to be O(1)

Ron.