Re: Real application clustering in postgres. - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Real application clustering in postgres.
Date
Msg-id 1aa5a345543ea85b3e0e7d3021ed6b1cdc04e66c.camel@cybertec.at
Whole thread Raw
In response to Real application clustering in postgres.  (Daulat Ram <Daulat.Ram@exponential.com>)
Responses RE: Real application clustering in postgres.  (Daulat Ram <Daulat.Ram@exponential.com>)
Re: Real application clustering in postgres.  (Ron <ronljohnsonjr@gmail.com>)
Re: Real application clustering in postgres.  (Andreas Kretschmer <andreas@a-kretschmer.de>)
List pgsql-general
On Thu, 2020-03-05 at 07:45 +0000, Daulat Ram wrote:
> Is there any possibility/options to setup a real application clustering in Postgres as in Oracle we have a  RAC
feature.

No, and as far as I know nobody feels interested in providing it.

RAC is a complicated architecture that doesn't do much good, so most
people feel that it would be a waste of time and effort.

RAC ist not really a scaling solution: because of the shared storage,
you can only scale for more CPUs; I/O remains the bottleneck.

RAC is not really a high availability solution: because of the shared
storage, it has a sibgle point of failure.

Today, people use shared-nothing architectures for high avaliability,
like Patroni.

> What about multi-master replication in Postgres. would you please suggest how it is useful and how can setup it.

There is no support for that in core PostgreSQL.

There is a closed-source implementation that you can buy:
https://www.2ndquadrant.com/en/resources/postgres-bdr-2ndquadrant/

But multi-master replication is complicated to get right, and
an applicatoin that uses it has to be specifically designed for that.
Very often a single-master failover solution is a better solution.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Determining the type of an obkect in plperl
Next
From: Alastair McKinley
Date:
Subject: Re: Poor plan choice with partial unique indexes on jsonb column andsimple RLS policy (with test script)