| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Stephen <jleelim(at)xxxxxx(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Some thoughts about i/o priorities and throttling vacuum |
| Date: | 2003-10-17 00:17:39 |
| Message-ID: | 16916.1066349859@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Of course, this makes VACUUM run longer, and if you are waiting for it
> to finish, it would be worse, like if you are running it at night or
> something.
> I think the delay has to take into account the number of active
> transactions or something.
I was just thinking of a GUC parameter: wait N milliseconds between
pages, where N defaults to zero probably. A user who wants to run his
vacuum as a background process could set N larger than zero. I don't
believe we are anywhere near being able to automatically adjust the
delay based on load, and even if we could, this would ignore the point
you make above --- the user's intent has to matter as much as anything
else.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-10-17 00:31:54 | Re: Bison 1.875 for SuSE Linux 8.1? |
| Previous Message | Tom Lane | 2003-10-17 00:04:30 | Re: postgres --help-config |