Just an FYI - this kind of thing would be a *great* feature addition to the generic PostgresSQL release. We at Lyris often hear that "postgressql is very slow, and the files are getting larger" and then "wow! it's so much faster now that we're regularly vacuuming!" after we let them know about this need (the RPM install of PostgresSQL is so easy that most people don't read any docs). Automatic maintenance of database tables is a Good Thing (tm) and would make more people we introduce to pgsql favorably disposed toward it.
> I have written a small daemon that can automatically vacuum PostgreSQL
> database, depending upon activity per table.
> It sits on top of postgres statistics collector. The postgres installation
> should have per row statistics collection enabled.
> Features are,
> * Vacuuming based on activity on the table
> * Per table vacuum. So only heavily updated tables are vacuumed.
> * multiple databases supported
> * Performs 'vacuum analyze' only, so it will not block the database
> The project location is
> Let me know for bugs/improvements and comments..
> I am sure real world postgres installations has some sort of scripts doing
> similar thing. This is an attempt to provide a generic interface to periodic
> The Abrams' Principle: The shortest distance between two points is off the
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
pgsql-hackers by date
|Next:||From: Joe Conway||Date: 2002-09-24 05:33:51|
|Subject: subselect bug (was Re: [GENERAL] DBLink: interesting issue)|
|Previous:||From: Gavin Sherry||Date: 2002-09-24 05:13:49|
|Subject: Re: Web site|