By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,904 Members | 1,089 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,904 IT Pros & Developers. It's quick & easy.

FW: Postgres: VACUUM

P: n/a
lnd
On heavily used databases (over 100,000 transactions an
hour), vacuum is
a killer


That's about 27 tx/second - not so many, for some tasks at least.

If VACUUM is rather a killer
- are any plans from PostgreSQL to deal with that?

Thank you in advance,
Laimis

P.S. it's notable that every DB system I delt with had one or another issue
as far as concurency is concerned, take infamous "Oracle-1555 snapshot too
old" error as an example.


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postgresql.org

Nov 22 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Wed, 14 Jan 2004 ln*@hnit.is wrote:
On heavily used databases (over 100,000 transactions an
hour), vacuum is
a killer


That's about 27 tx/second - not so many, for some tasks at least.

If VACUUM is rather a killer
- are any plans from PostgreSQL to deal with that?


Yes, Tom and friends have been tossing back and forth a patch to implement
a sleep between x number of pages being vacuumed to remove the heavy load
vacuum can place on a system. Early testing looks promising, so it's
likely that if enough of us order Tom or somebody a pizza it will get
done. :-) I certainly would like to see it.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 22 '05 #2

P: n/a
ln*@hnit.is writes:
On heavily used databases (over 100,000 transactions an hour),
vacuum is a killer


That's about 27 tx/second - not so many, for some tasks at least.

If VACUUM is rather a killer
- are any plans from PostgreSQL to deal with that?


Yes. There is a patch available that causes VACUUM to sleep() after
every few pages it processes, which throttles VACUUM's ill effects on
cache. It isn't yet in 7.4.1, but might be in a later 7.4 release.

There is also a major revision taking place (look up "ARC" on the
hackers list) for management of cache that should also be helpful.
--
let name="cbbrowne" and tld="libertyrms.info" in String.concat "@" [name;tld];;
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 646 3304 x124 (land)
Nov 22 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.