Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] autovacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-admin(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] autovacuum
Date: 2006-02-01 18:18:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-hackers
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


pgsql-hackers by date

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

pgsql-admin by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group