Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> During btree index build, sort equal-keyed tuples according to their
> >> TID (heap position). This doesn't do anything to the validity of the
> >> finished index, but by pretending to qsort() that there are no really
> >> equal keys in the sort, we can avoid performance problems with qsort
> >> implementations that have trouble with large numbers of equal keys.
> >> Patch from Manfred Koizar.
> > I think there is also the advantage that many equal keys will access the
> > heap in a more sequential, rather than random, order, which is the part
> > that really excited me.
> But we aren't attempting to maintain that ordering after index build.
> (In fact, it was exactly that point that triggered the argument last
> time round ...)
Agreed, but we don't maintain CLUSTER either. I see no harm in having
it start out ordered, at least.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2004-03-18 03:56:59|
|Subject: pgsql-server/src/tools/fsync Makefile README t ...|
|Previous:||From: Tom Lane||Date: 2004-03-18 00:37:01|
|Subject: Re: pgsql-server/src/backend/utils/sort tuplesort.c |