| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> | 
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Vacuuming and already vacuumed table? | 
| Date: | 2003-08-29 03:58:46 | 
| Message-ID: | 1062129525.10184.45.camel@zeutrh9 | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Thu, 2003-08-28 at 16:53, 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.
7.4Beta has a contrib module called pg_autovacuum.  It attempts to do
exactly what you are talking about.  It only vacuums a table that has
had sufficient activity since the last vacuum.  It runs as a standalone
daemon.  Also, it can be used against 7.3 if that is what you are
running.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2003-08-29 03:59:30 | Re: Fast Table Replication / Mirroring | 
| Previous Message | Alex | 2003-08-29 03:49:21 | Fast Table Replication / Mirroring |