| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | jim(at)nasby(dot)net |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: More tablescanning fun |
| Date: | 2003-04-25 16:28:06 |
| Message-ID: | 1051288086.1765.95.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2003-04-25 16:56:13 | Re: More tablescanning fun |
| Previous Message | Jim C. Nasby | 2003-04-25 15:09:05 | Re: Important speed difference between a query and a function with the same query |