Re: pgsql is 75 times faster with my new index scan

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: "'devik(at)cdi(dot)cz'" <devik(at)cdi(dot)cz>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql is 75 times faster with my new index scan
Date: 2000-09-27 06:41:18
Message-ID: 39D1968E.C1B68213@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Mikheev, Vadim" wrote:
>
> Why not implement *true* CLUSTER?
> With cluster, all heap tuples will be in cluster index.
>

What is *true* CLUSTER ?

'grep CLUSTER' over the latest SQL standards gives back nothing.

> > > The last step could be done in two ways. First by limiting
> > > number of indices for one table we can store coresponding
> > > indices' TIDs in each heap tuple. The update is then simple
> > > taking one disk write.
> >
> > Why limit it ? One could just save an tid array in each tuple .
>
> And update *entire* heap after addition new index?!

I guess that this should be done even for limited number of
indices' TIDs in a heap tuple ?

--------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Louis-David Mitterrand 2000-09-27 06:53:58 function crashes backend
Previous Message Hannu Krosing 2000-09-27 06:31:43 Re: use of / in ~ vs. ~*