For large tables that require a 24/7 uptime and see around 6-10 million changes a day, how do I run VACUM without taking the database/table down. Considering moving from MySQL, but can't quite understand how to run PostgreSQL in a production enviroment properly. August ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
- Re: [ADMIN] Recommended VACUM timing... August Zajonc
- Re: [ADMIN] Recommended VACUM timing... David Lizano
- RE: [ADMIN] Recommended VACUM timing... Matthew