Re: Pre-allocated free space for row - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Pre-allocated free space for row
Date
Msg-id 1125483531.5168.16.camel@fuji.krosing.net
Whole thread Raw
In response to Re: Pre-allocated free space for row updating (like PCTFREE)  (Satoshi Nagayasu <nagayasus@nttdata.co.jp>)
Responses Re: Pre-allocated free space for row  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On K, 2005-08-31 at 16:50 +0900, Satoshi Nagayasu wrote:
> Simon Riggs wrote:
> >>4. Allow to repair fragmentation in each page.
> >>
> >>Because updates cause fragmentation in the page.
> >>
> >>So we need to keep large continuous free space in each page,
> >>if we want to get more effective on PCTFREE feature.
> > 
> > 
> > ...doesn't VACUUM already do that?
> 
> VACUUM generates a huge load because it repaires all pages
> on the table file.
> 
> I think (more light-weight) repairing on a single page
> is needed to maintain free space in the specific page.

There have been plans floating around for adding a more lightweight
vacuum, which uses something similar to FSM to keep track of pages which
need vacuuming. And possibly integreated with background writer to make
effective use of I/O resources.

I guess it could be used for this case of "cheap page cleanups" as well.

-- 
Hannu Krosing <hannu@skype.net>



pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: ERROR: bogus varno: 1 with 8.1beta and postgis 1.0.3
Next
From: Dawid Kuroczko
Date:
Subject: Re: Call for 7.5 feature completion