I don't mind the long delay as long as we have a choice as we clearly do in
this case to set vacuum_page_delay=WHATEVER. Of course, if VACUUM can be
improved with better code placement for the delays or buffer replacement
policies then I'm all for it. Right now, I'm pretty satisfied with the
responsiveness on large DBs using vacuum_page_delay=10ms delay.
Any ideas if this patch will be included into 7.4 before final release?
"Andrew Dunstan" <andrew(at)dunslane(dot)net> wrote in message
> Not surprising, I should have thought. Why would you care that much?
> The idea as I understand it is to improve the responsiveness of things
> happening alongside vacuum ("real work"). I normally run vacuum when I
> don't expect anything else much to be happening - but I don't care how
> long it takes (within reason), especially if it isn't going to intefere
> with other uses.
In response to
pgsql-hackers by date
|Next:||From: Jan Wieck||Date: 2003-11-03 15:33:21|
|Subject: Experimental ARC implementation|
|Previous:||From: Tom Lane||Date: 2003-11-03 15:04:39|
|Subject: Re: equal() perf tweak |