On Fri, Aug 21, 2009 at 10:46 AM, james bardin wrote:
> The first move runs easily as expected- postgres ships the last
> partial wal immediately on shutdown, trigger the standby and we're up.
> I'm now running into issues bringing the first server back up in
> standby
Hello,
I have a working warm standby system, running 8.4 (thanks for urging
me to upgrade from the rehdat provided release).
One of the new requirements is going to be for (a non-DBA) admin to
easily swap services between the two servers for maintenance.
The first move runs easily as expected- po
Thanks Ken. The more I think about it, the more I feel we should move
away from upstream, and pull the latest version for this.
So on with newer versions -
When using the built-in systems for warm standby, how do I ensure that
the latest transactions have been archived? Does a clean shutdown
flus
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, o
