Re: Free space mapping (was Re: Multi-Versions and Vacuum)

From: grant <grant(at)amadensor(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Sullivan <andrew(at)libertyrms(dot)info>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Date: 2002-07-19 20:21:30
Message-ID: Pine.LNX.4.33.0207191311510.29118-100000@dbms.amadensor.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

So, then, even if there is an overflow of pages with free space, stepping
up the vacuum schedule may help this eventually catch up.

As for an automated way to set this up, if the FSM size cannot be adjusted
without a restart of the postmaster, then on startup, you could take a
number of pages currently with free space or a percentage of the number of
pages, which ever is greater. The percentage could have a default, and
also be configurable.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message chris.gamble 2002-07-19 20:45:58 currval sequence memory storage?
Previous Message Tom Lane 2002-07-19 20:16:53 Re: [SQL] id and ID in CREATE TABLE