From: | Ray Stell <stellr(at)cns(dot)vt(dot)edu> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, Galy Lee <lee(dot)galy(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-performance(at)postgresql(dot)org, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] how to plan for vacuum? |
Date: | 2007-01-25 16:33:29 |
Message-ID: | 20070125163329.GD19599@cns.vt.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Thu, Jan 25, 2007 at 08:04:49AM -0800, Joshua D. Drake wrote:
>
> It really depends on the system. Most of our systems run anywhere from
> 10-25ms. I find that any more than that, Vacuum takes too long.
How do you measure the impact of setting it to 12 as opposed to 15?
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Samokhvalov | 2007-01-25 16:35:25 | Re: tsearch in core patch, for inclusion |
Previous Message | Joshua D. Drake | 2007-01-25 16:31:21 | Re: tsearch in core patch, for inclusion |
From | Date | Subject | |
---|---|---|---|
Next Message | John Parnefjord | 2007-01-26 11:28:19 | Tuning |
Previous Message | Jim C. Nasby | 2007-01-25 16:22:47 | Re: [PERFORM] how to plan for vacuum? |