> >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.
>
>
> a) Using replic
>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.
a) Using replication, you ca
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
---
