Re: Autovacuum in the backend

From: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Autovacuum in the backend
Date: 2005-06-17 09:01:15
Message-ID: 200506171901.16148.mr-russ@pws.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> Added to TODO:
>
> * Create a bitmap of pages that need vacuuming
>
> Instead of sequentially scanning the entire table, have the background
> writer or some other process record pages that have expired rows, then
> VACUUM can look at just those pages rather than the entire table. In
> the event of a system crash, the bitmap would probably be invalidated.
>
Further to this, is there any use case for allowing FSM, or this DSM to spill to disk
if the space fills up. It would allow the possibility of unusual changes to the db
to not loose space. You could just load part of the overflow from the disk back
int the FSM in memory and continue using free space.

Regards

Russell Smith

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Russell Smith 2005-06-17 09:05:01 Re: Autovacuum in the backend
Previous Message Russell Smith 2005-06-17 08:56:17 Re: Autovacuum in the backend

Browse pgsql-hackers by date

  From Date Subject
Next Message Russell Smith 2005-06-17 09:05:01 Re: Autovacuum in the backend
Previous Message Andreas Pflug 2005-06-17 08:58:08 Re: Utility database (Was: RE: Autovacuum in the backend)