On Thu, Apr 29, 2010 at 9:07 AM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > Robert Haas wrote: >> How about this one? The administrator sets up a master and a slave. >> She's heard about this new Hot Standby feature and so decides to >> enable it on the slave just to play around with it. Subsequently, she >> takes a better job at another company and they hire a new >> administrator, who thinks the Hot Standby WAL may be causing a >> performance problem on the master, so he switches wal_mode to archive. >> Six months later the primary fails. > > Umm, I don't see the problem. For high availability purposes, the > standby works just as well with wal_mode='archive'. Or are you saying > that the standby was configured with recovery_connections='on', and > failed to start for those six months because hot standby could not be > enabled, and no-one noticed?
Yep. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
