On Mon, Sep 20, 2010 at 3:27 PM, Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> wrote: > However, the "wait forever" behavior becomes useful if you have a monitoring > application outside the DB that decides when enough is enough and tells the > DB that the slave can be considered dead. So "wait forever" actually means > "wait until I tell you that you can give up". The monitoring application can > STONITH to ensure that the slave stays down, before letting the master > proceed with the commit.
This is also useful for preventing a failover from causing some data loss by promoting the lagged standby to the master. To avoid any data loss, we must STONITH the standby before any transactions resume on the master, when replication connection is terminated or the crash of the standby happens. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
