Going with your first option, a master->slave replication, has the
added benefit that you build the expertise for doing Continuous Point
In Time Recovery, and after you do this storage system migration you
can use that knowledge to put in a place a permanent standby server.
Yes, it is a bit of work
These functions aren't actually doing anything overly magical. They
don't cause you to end up with a "nice clean snapshot", at least not
right away. They're mostly just helping with the housekeeping tasks of
making sure that in the future you have kept around the WAL segments
that will be necessar
Postgres Admin Wizards,
I am trying to manage an 8.4 database whose ingest rate is
sufficiently high that doing base backups on it causes it to fall
unacceptably behind. To deal with this, I want to do WAL shipping to
another server that is in warm standby mode, and then on that server
perform th
