Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
We are about to go live with a DRBD / PostgreSQL installation running on Debian 5, 2.6.26-2-amd64. Is there a way to prevent write operations on the Primary in case it loses connection with the Secondary? Why would I want to do that? Because if the Primary goes down, while the Secondary is in state UpToDate/DUnknown, it is not possible to know for sure if the Primary has been modified after the Secondary lost its connection with the Primary. But if the Primary would refuse to perform any write operations if the replication link goes down to the Secondary, it would be totally safe to promote the Secondary to Primary. I do of course realize such a configuration would mean the entire system would become inaccessible if the Secondary would go down, but that is also my wish since we cannot risk losing any data. Any ideas are welcome. Thanks. -- View this message in context: http://www.nabble.com/Howto-prevent-write-operations-on-Primary-when-in-WFConnection-tp25703586p25703586.html Sent from the DRBD - User mailing list archive at Nabble.com.