public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jim C. Nasby <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Dawid Kuroczko <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [HACKERS] Replication documentation addition
Date: Thu, 26 Oct 2006 10:55:36 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > Something else worth doing though is to have a paragraph explaining why
> > there's no built-in replication. I don't have time to write something
> > right now, but I can do it later tonight if no one beats me to it.
>
> I thought that was implied in the early paragraph about why there are
> many solutions.
I think we should explicitely spell it out, especially considering how
many times people ask about it. How about...
This multitude of choices is why PostgreSQL does not ship with a
replication solution by default; any bundled solution would only
satisfy a subset of replication needs.
(sorry for the non-standard patch, but anoncvs isn't sync'd up yet).
--
Jim Nasby [email protected]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
*** failover.sgml.org Thu Oct 26 10:32:45 2006
--- failover.sgml Thu Oct 26 10:55:03 2006
***************
*** 29,35 ****
working together. Because there is no single solution that eliminates
the impact of the sync problem for all use cases, there are multiple
solutions. Each solution addresses this problem in a different way, and
! minimizes its impact for a specific workload.
</para>
<para>
--- 29,37 ----
working together. Because there is no single solution that eliminates
the impact of the sync problem for all use cases, there are multiple
solutions. Each solution addresses this problem in a different way, and
! minimizes its impact for a specific workload. This multitude of choices is
! why PostgreSQL does not ship with a replication solution by default; any
! bundled solution would only satisfy a subset of replication needs.
</para>
<para>
Attachments:
[text/plain] patch (911B, 2-patch)
download | inline:
*** failover.sgml.org Thu Oct 26 10:32:45 2006
--- failover.sgml Thu Oct 26 10:55:03 2006
***************
*** 29,35 ****
working together. Because there is no single solution that eliminates
the impact of the sync problem for all use cases, there are multiple
solutions. Each solution addresses this problem in a different way, and
! minimizes its impact for a specific workload.
</para>
<para>
--- 29,37 ----
working together. Because there is no single solution that eliminates
the impact of the sync problem for all use cases, there are multiple
solutions. Each solution addresses this problem in a different way, and
! minimizes its impact for a specific workload. This multitude of choices is
! why PostgreSQL does not ship with a replication solution by default; any
! bundled solution would only satisfy a subset of replication needs.
</para>
<para>
view thread (117+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] Replication documentation addition
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox