| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rob Nagler <nagler(at)bivio(dot)biz> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: vacuum locking |
| Date: | 2003-10-30 17:28:47 |
| Message-ID: | 1113.1067534927@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Rob Nagler <nagler(at)bivio(dot)biz> writes:
> When vacuum is running, it's going through the entire
> database, and that pretty much trashes all other queries, especially
> DSS queries. As always it is just software, and there's got to be
> 80/20 solution.
One thing that's been discussed but not yet tried is putting a tunable
delay into VACUUM's per-page loop (ie, sleep N milliseconds after each
heap page is processed, and probably each index page too). This might
be useless or it might be the 80/20 solution you want. Want to try it
and report back?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-10-30 17:55:32 | Re: vacuum locking |
| Previous Message | CLeon | 2003-10-30 17:28:10 | Re: [linux-lvm] RE: [PERFORM] backup/restore - another |