On 03/21/2016 10:57 AM, Thomas Kellerer wrote:
So - at least as far as I can tell - it's usually only used where high-availability is really important, e.g. where zero-downtime is required. If you can live with a short downtime, a hot standby is much cheaper and probably not that much slower.
Even the above statement can be challenged , given the rising popularity of nosql databases which are all based on
eventual consistency (aka async replication). A PG with BDR and an application designed to read/write only one node via connection mapping can match the high availability requirement of RAC. BTW disk is a single point of failure in RAC. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
