On October 10th, 2007 Decibel (not verified) says:
It's very easy to control the impact of vacuum via the vacuum_cost settings.
And "never being able to finish" is nothing but FUD. Other databases have a similar amount of work to do, they just do it during the transaction itself. At least with PostgreSQL you have the ability to put that work off until later.
Finally, in almost any *real* benchmark, PostgreSQL is more scalable than MySQL. So unless you're doing something that's essentially single-user, PostgreSQL will be faster.
It's very easy to control
It's very easy to control the impact of vacuum via the vacuum_cost settings.
And "never being able to finish" is nothing but FUD. Other databases have a similar amount of work to do, they just do it during the transaction itself. At least with PostgreSQL you have the ability to put that work off until later.
Finally, in almost any *real* benchmark, PostgreSQL is more scalable than MySQL. So unless you're doing something that's essentially single-user, PostgreSQL will be faster.