> From 7.3 to 7.4 the biggest changes planned so far:
> - windows native support <-- gartner gives it a 90% chance of making it
> into the main disto... :-)
> - fix for in() performance issue <-- already in CVS tip
> - partitioning or tablespaces <-- who know? seriously, who?
> - vacuum will be able to compact out unused space <-- Tom Lane
Will we be able to run the new vacuum system without locking the tables?
Currently our database is at about 15gigs. Over the period of a month,
it grows to about 25gigs (10Gb wasted space). Every month we have a
cleanup routine which involves copying the most actively updated tables
to text, and importing the data again. We vacuum every night and analyze
4 times per day, but we're loath to do a VACUUM FULL because of the
table locking issues (locking some of the tables would break the
operation of some of our 24/7 systems), hence we prefer to stop the db
about once per month, eat the downtime as scheduled (about 1.5 hours),
and get back to business for the next 30 days again.
We're all behind Tom on this change :-)
- Ericson Smith
eric@did-it.com
--
Ericson Smith <eric@did-it.com>
