Re: Visibility map, partial vacuums - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Visibility map, partial vacuums
Date
Msg-id 200901151548.n0FFmr204820@momjian.us
Whole thread Raw
In response to Re: Visibility map, partial vacuums  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Visibility map, partial vacuums  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas wrote:
> >> Also, is anything being done about the concern about 'vacuum storm'
> >> explained below?
> > 
> > I'm interested too.
> 
> The additional "vacuum_freeze_table_age" (as I'm now calling it) setting 
> I discussed in a later thread should alleviate that somewhat. When a 
> table is autovacuumed, the whole table is scanned to freeze tuples if 
> it's older than vacuum_freeze_table_age, and relfrozenxid is advanced. 
> When different tables reach the autovacuum threshold at different times, 
> they will also have their relfrozenxids set to different values. And in 
> fact no anti-wraparound vacuum is needed.
> 
> That doesn't help with read-only or insert-only tables, but that's not a 
> new problem.

OK, is this targeted for 8.4?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: tuplestore potential performance problem
Next
From: Peter Eisentraut
Date:
Subject: Re: FWD: Re: Updated backslash consistency patch