Renato Oliveira wrote:
Are there any commercial solutions out there for migrating large DBs?
I'm not aware of any. The main way to address this problem by throwing money at it is to hire someone extremely familiar with PostgreSQL replication technology and figure out how to customize one of the available approaches (Slony, Londiste, PITR, dump/restore) to match your application. For example, in some cases it's possible to record database changes on the application side, replicate the database via one of the fast online approaches like PITR, and then synchronize just the changes made in the master while that was happening for a fast switch-over to a new version. It's not unheard for that to require small application changes to support, to provide an easier way to log the difference between the two.
If you can't take the additional load of Slony and have minimal tolerance for downtime, you really need to come up with a long-term approach to coping with that from an application architecture perspective. Unfortunately you're not going to find any quick fix for that combination of requirements.
-- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
