Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Hmm, yeah, sounds useful.  There's one implementation issue to notice
> however, and it's that the autovacuum process dies and restarts for each
> iteration, so there's no way for it to remember previous state unless
> it's saved somewhere permanent, as the stats info is.

I think you'd really need to remember the previous oldest XID on a
per-table basis to get full traction out of the idea.  But weren't we
thinking of tracking something isomorphic to this for purposes of
minimizing anti-wraparound VACUUMs?

			regards, tom lane

In response to

• Re: [HACKERS] autovacuum at 2006-02-01 17:29:05 from Alvaro Herrera

Responses

• Re: autovacuum at 2006-02-01 19:51:36 from Chris Browne

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2006-02-01 18:22:17
	Subject: Re: TODO-Item: B-tree fillfactor control
Previous:	From: Chris Browne	Date: 2006-02-01 17:54:42
	Subject: Re: autovacuum

pgsql-admin by date

Next:	From: Chris Browne	Date: 2006-02-01 19:51:36
	Subject: Re: autovacuum
Previous:	From: Chris Browne	Date: 2006-02-01 17:54:42
	Subject: Re: autovacuum