> 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.
