On Tue, Mar 20, 2012 at 1:33 PM, amador alvarez <aalvarez@xxxxxx> wrote: > I wonder why are you considering this solution, as if something wrong comes > within the data (logical corruption, user error) it will be spread on both > locations, Would not be better a delayed standby database. That's a risk, to be sure. That's why you also keep backups (such as a PITR slave). If you're doing HA without also doing backups, you're Doing It Wrong. The benefit of Shared Storage clustering is immediate availability if your "primary" node goes down for some reason. You simply fence off the downed node, mount the shared volume, and bring up the db on the secondary node. I've used commercial solutions that manage all this, and reliably have the DB back in service in tens of seconds, at the outside. rls -- :wq -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
