Re: Multi Master Replication

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Multi Master Replication
Date: 2013-12-19 06:05:58
Message-ID: CAOR=d=1daWHDKLga=xL=450Xv7NuGn7mF4Pab8kDYc3CBvTMcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 18, 2013 at 10:25 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:

> On Thu, Dec 19, 2013 at 7:12 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:

>> When people start talking multi-master replication my first response
>> is to ask what problem you're trying to solve. Sometimes MM Rep IS the
>> answer. But quite often it's not the best one for your problem. So to
>> OP I'd ask what problem they're trying to solve.

> Yes that's actually the right approach, multi-master replication is
> often cited as a marketing term for a fantastic technology that can
> solve a lot of problems, which could be solved with a couple of
> Postgres servers using a single-master, multiple-slave approach, or by
> simply design a system that can do data sharding among a set of
> Postgres servers to achieve some kind of write scalability.

Sharding with plproxy is pretty easy and can scale hugely.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Amit Langote 2013-12-19 06:24:09 Re: unexpected pageaddr error in db log
Previous Message Bob Futrelle 2013-12-19 05:36:00 Installed postgres.app 9.3.1.0. pgadmin doesn't appear to see it