Re: Autovacuum in the backend - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: Autovacuum in the backend
Date
Msg-id 1118825769.4844.25.camel@fuji.krosing.net
Whole thread Raw
In response to Re: Autovacuum in the backend  ("Qingqing Zhou" <zhouqq@cs.toronto.edu>)
Responses Re: Autovacuum in the backend
List pgsql-hackers
On K, 2005-06-15 at 13:41 +0800, Qingqing Zhou wrote:
> "Neil Conway" <neilc@samurai.com> writes
> >
> > Wasn't the plan to rewrite pg_autovacuum to use the FSM rather than the
> > stats collector?
> >
> 
> I don't understand. Currently the basic logic of pg_autovacuum is to use the
> pg_stat_all_tables numbers like n_tup_upd, n_tup_del to determine if a
> relation need to be vacuumed. How to use FSM to get these information?

One can't probably use FSM as it is, as FSM is filled in by vacuum and
this creates a circular dependency.

But it would be very nice to have something _similar_ to FSM, say DSM
(dead space map), which is filled in when a tuple is marked as "dead for
all running backends", which could be used to implement a vacuum which
vacuums only those pages, which do actually contain removable tuples.

-- 
Hannu Krosing <hannu@skype.net>



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Autovacuum in the backend
Next
From: "Qingqing Zhou"
Date:
Subject: Re: Autovacuum in the backend