From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Future In-Core Replication |
Date: | 2012-04-30 18:55:00 |
Message-ID: | CA+U5nMLzmKyMgUPYH44FF-gPGFcCHYW1QnF46Bu6yS4PgxOivA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 30, 2012 at 6:38 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I would love to see a layout of exactly where these things make sense,
> similar to what we do at the bottom of our documentation for "High
> Availability, Load Balancing, and Replication":
>
> http://www.postgresql.org/docs/9.1/static/different-replication-solutions.html
>
> Users and developers just can't seem to get the calculus of where things
> make sense into their heads, me included.
>
> For example, you said that "MM replication alone is not a solution for
> large data or the general case". Why is that? Is the goal of your work
> really to do logical replciation, which allows for major version
> upgrades? Is that the defining feature?
Good question.
The use case, its breadth and utility are always the first place I
start. I'm in the middle of writing a presentation that explains this
from first principles and will be discussing that at the PgCon
meeting. It's taken a long time to articulate that rather than make
leaps of assumption and belief.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-04-30 19:01:54 | Re: Analyzing foreign tables & memory problems |
Previous Message | Albe Laurenz | 2012-04-30 18:50:04 | Re: Analyzing foreign tables & memory problems |