Re: More tablescanning fun - Mailing list pgsql-performance

From Tom Lane
Subject Re: More tablescanning fun
Date
Msg-id 29560.1051301447@sss.pgh.pa.us
Whole thread Raw
In response to Re: More tablescanning fun  (Hannu Krosing <hannu@tm.ee>)
List pgsql-performance
Hannu Krosing <hannu@tm.ee> writes:
> I have been pondering if keeping pages half-empty (or even 70% empty)
> could solve both clustering problems and longish updates for much data.

You could achieve that pretty easily if you simply don't ever VACUUM
FULL ;-)

UPDATE has always (AFAIR) attempted to place the new version on the same
page as the old, moving it elsewhere only if it doesn't fit.  So that
part of the logic is already there.

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

Not so much that, as a parameter to CLUSTER telling it to fill pages
only x% full.

            regards, tom lane


pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: More tablescanning fun
Next
From: "Cecilia Alvarez"
Date:
Subject: Indexes with different datatypes