Thanks, Brian & Jaime. Regarding Slony, would that allow for
migration to a new version as well - i.e. moving from 8.2 on the old
machine to 8.4 on the new machine via Slony with minimal downtime?
The Slony method is one I hadn't considered. Since our database is so
large, even a direct file copy would require some downtime (since we'd
need to stop the DB before beginning the copy). Slony would probably
let us cut the downtime from hours to minutes (dump & restore for us
has historically taken days).
Thanks again,
Evan
