Re: More tablescanning fun - Mailing list pgsql-performance

From Hannu Krosing
Subject Re: More tablescanning fun
Date
Msg-id 1051288086.1765.95.camel@fuji.krosing.net
Whole thread Raw
In response to Re: More tablescanning fun  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: More tablescanning fun
Re: More tablescanning fun
List pgsql-performance
Jim C. Nasby kirjutas R, 25.04.2003 kell 07:59:
> > > Also, is there a TODO to impliment
> > > real clustered indexes?
> >
> > No.  It's not apparent to me how you could do that without abandoning
> > MVCC, which we're not likely to do.
>
> Hmm... does MVCC mandate inserts go at the end?

I have been pondering if keeping pages half-empty (or even 70% empty)
could solve both clustering problems and longish updates for much data.

If we could place the copy in the same page than original, most big
updates would be possible by one sweep of disk heads and also clustering
order would be easier to keep if pages were kept intentionally half
empty.

So "VACUUM FULL 65% EMPTY;" could make sense ?


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


pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Important speed difference between a query and a function with the same query
Next
From: "Jim C. Nasby"
Date:
Subject: Re: More tablescanning fun