Re: PostgreSQL advocacy - Mailing list pgsql-general

From Rakesh Kumar
Subject Re: PostgreSQL advocacy
Date
Msg-id 56F01CEE.8050803@gmail.com
Whole thread Raw
In response to Re: PostgreSQL advocacy  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: PostgreSQL advocacy  ("Jernigan, Kevin" <kmj@amazon.com>)
List pgsql-general
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-downtimeis 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.


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: [SQL] plan not correct?
Next
From: "Jernigan, Kevin"
Date:
Subject: Re: PostgreSQL advocacy