James, You really, really, really should upgrade to a more recent release. The list of improvements and bugfixes is long and well worth having. 8.1 was released 4 years ago. If you cannot, please, please make certain that you are running the latest point release -- regardless of what is shipping with RHEL5. Good luck, Ken On Tue, Aug 18, 2009 at 11:27:40AM -0400, james bardin wrote: > Hello, > > I'm working on a warm standby system, and we would like to stick with > the RHEL5 distributed version of postgres, which is still 8.1. > > I can setup the system to a point where it's adequate for disaster > recovery, but I'm not comfortable keeping the systems in sync for > failover, maintenance, or testing. I'm familiar with the newer > versions, and most documentation for this doesn't mention 8.1 any > more. > > Could someone confirm if this is what I need to do on 8.1? > - Create backup, and send to standby server. > - Ship WALs with archive_command > - When we need to switch over; shutdown, sync pg_xlog, and do a > recovery on the new server. > > If I have to sync pg_xlog and recover anyway to get the latest > transactions, should I forgo shipping the WAL archives? Switching > between servers should be rare, but I want something that admins > without postgres experience can handle. > > Should I resort to slony? > Use the latest version from the postgres yum repo, and vet it locally? > > Thanks > -jim > > -- > Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
