The changes in PostgreSQL 9 allow for "hot standby" databases, which are running and allow read-only access and can instantly become stand-alone masters if failover is needed. You can have many standby DBs being fed by one master with little performance degradation. The slaves are updated asynchronously, so this is an "eventually consistent" architecture; but in practice the slaves are updated almost instantly after the master, so it's pretty close.
This built-in stuff is just one possible approach to implementing replication. There are many alternative, third party approaches that are widely used as well that have different characteristics; not better or worse, just different. John On Fri, Jul 29, 2011 at 10:42 AM, Miguel Arroz <[email protected]> wrote: > Hi, > > Postgresql introduced built-in decent replication (master-slave) in > version 9. I never used it, by according to what I read about it, seems it > was done the way it should be. >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
