From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Vacuuming and already vacuumed table? |
Date: | 2003-08-29 02:30:24 |
Message-ID: | m37k4xjiv3.fsf@chvatal.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In the last exciting episode, sfrost(at)snowman(dot)net (Stephen Frost) wrote:
> Would it make sense for vacuum to keep a list of 'last vacuumed' or
> similar so that it doesn't vacuum a table which hasn't changed since
> the last time it was vacuum'd? Seems to me that would be a pretty
> simple optimization which would help out alot on systems which have
> both a large set of tables which are relatively static and data which
> changes a great deal. This is especially true for vacuum full which
> also locks the table.
See, in 7.4, the "pg_autovacuum" daemon.
It does much what you suggest...
--
(format nil "~S(at)~S" "cbbrowne" "ntlug.org")
http://www.ntlug.org/~cbbrowne/finances.html
Rules of the Evil Overlord #110. "I will not employ devious schemes
that involve the hero's party getting into my inner sanctum before the
trap is sprung." <http://www.eviloverlord.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Ursula Lee | 2003-08-29 02:39:12 | Unsubscribe from the list |
Previous Message | Browne, George (AT-Atlanta) | 2003-08-29 02:23:18 | How does it work |