| From: | Hannu Krosing <hannu(at)skype(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>, Shelby Cain <alyandon(at)yahoo(dot)com>, Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Subject: | Re: Autovacuum in the backend |
| Date: | 2005-06-15 08:50:42 |
| Message-ID: | 1118825442.4844.20.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On T, 2005-06-14 at 21:23 -0400, Bruce Momjian wrote:
> One goal for 8.1 is to move /contrib/pg_autovacuum in to the backend. I
> think it has to be done in four stages:
>
> o move it into the backend and have it start/stop automatically
> o move the autovacuum configuration parameters into postgresql.conf
> o modify the code to use the backend API for error recovery
> o modify the code to use the backend API utilities, like hashes
>
> Who would like to get started on this? It seems pretty straight-forward.
Can autovacuum yet be configured _not_ to run vacuum during some hours
or above some load ?
Even better - to stop or pause a long-running vacuum if load goes above
some limit.
If it goes into backend before the above is done, it should at least be
possible to switch it off completely.
--
Hannu Krosing <hannu(at)skype(dot)net>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-06-15 08:56:09 | Re: Autovacuum in the backend |
| Previous Message | Richard Huxton | 2005-06-15 06:08:02 | Re: Database became very slow(Help PLS) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2005-06-15 08:56:09 | Re: Autovacuum in the backend |
| Previous Message | Dennis Bjorklund | 2005-06-15 08:42:46 | Re: LGPL |