On Friday, March 25, 2011 03:35:29 pm Les Mikesell wrote: > If 'get there' is defined as all redundant copies being in a consistent > state, then you'll fail at this point in transactional mode in the > fairly likely event that you have a network blip between the db master > and slave(s) or one of them is down. Puh-lease. TCP has solved that problem; look into the new algorithms and techniques PostgreSQL 9 brings to the ACID table. Networks at layer 3 are expected to blip; TCP at layer 4 makes it a reliable stream. Or if it goes down both endpoints know it went down, and the database engine has a choice whether to abort and rollback or wait on a retry. Replay write-ahead logs are another way to deal with this.