>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
I did ask a similiar question previously.
There doesn't seem to be any widely used replication systems for
postgresql. As far as I can see.
Here's my plan.
1) Nightly, shutdown the postgresql service until a complete pg_dump is obtained.
2) Move and update a second machine with the data from pg
