Re: Pre-allocated free space for row updating (like PCTFREE)

From: Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Pre-allocated free space for row updating (like PCTFREE)
Date: 2005-08-31 07:50:14
Message-ID: 43156136.9040600@nttdata.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
NAGAYASU Satoshi <nagayasus(at)nttdata(dot)co(dot)jp>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2005-08-31 09:27:16 Re: ERROR: bogus varno: 1 with 8.1beta and postgis 1.0.3
Previous Message rm_pg 2005-08-31 07:30:55 ERROR: bogus varno: 1 with 8.1beta and postgis 1.0.3