| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | Hannu Krosing <hannu(at)skype(dot)net>, 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> |
| Subject: | Re: Autovacuum in the backend |
| Date: | 2005-06-15 20:21:30 |
| Message-ID: | 200506152021.j5FKLUE05388@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Matthew T. O'Connor wrote:
> I don't think the current implementation if VACUUM can support that. I
> believe that all the work will get rolled back if gets canceled.
>
> Perhaps a decent solution would be to have autovacuum increase the
> vacuum delay settings dynamically based on system load average. That
> way if a vacuum starts and the system starts to get busy, the autoavcuum
> daemon can increase the vacuum delay settings and VACUUM would honor
> this while running.
I would like to have the GUC variables be honored while the system is
running, and that would all administrators to make changes from scripts.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-06-15 20:22:14 | Re: return two elements |
| Previous Message | uruz | 2005-06-15 20:02:43 | graphic client |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2005-06-15 21:18:25 | Re: INHERITS and planning |
| Previous Message | Matthew T. O'Connor | 2005-06-15 20:02:34 | Re: Autovacuum in the backend |